Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=642683
inspired from:
https://git.gnome.org/browse/evince/commit/?id=392d8e3
https://git.gnome.org/browse/evince/commit/?id=e656398
|
|
Metadata won't be saved in those cases, but default settings will
applied.
https://bugzilla.gnome.org/show_bug.cgi?id=680145
taken from:
https://git.gnome.org/browse/evince/commit/shell/ev-window.c?h=gnome-3-6&id=6d25b93
|
|
Remember the folder last used to open or save a document, attachment
or image.
taken from:
https://git.gnome.org/browse/evince/commit/shell/ev-window.c?h=gnome-3-6&id=f6137df22503d88a76cc69f622919ec7bd3582d7
shell: Fix potential read-after-free in gsettings use
It's not valid to use '&' with g_settings_get().
https://bugzilla.gnome.org/show_bug.cgi?id=723737
taken from:
https://git.gnome.org/browse/evince/commit/?id=41ce0e1
ev-window: Don't crash when trying to save a copy
We can not free both folder_uri and parent_uri. If parent_uri is
non-NULL then it will point to the same location as folder_uri.
Also, parent_uri is now unused so we can just remove it.
https://bugzilla.gnome.org/show_bug.cgi?id=727536
taken from:
https://git.gnome.org/browse/evince/commit/?id=3850ff5
|
|
Fixes bug 655514.
taken from:
https://git.gnome.org/browse/evince/commit/shell/ev-window.c?h=gnome-3-8&id=55c1f8231bdab143a1d90f4bd598852d746b08e0
|
|
It doesn't make sense anymore since we have multiple processes.
taken from:
https://git.gnome.org/browse/evince/commit/shell/ev-window.c?h=gnome-3-2&id=3df6a61
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=669265
taken from:
https://git.gnome.org/browse/evince/commit/shell/ev-window.c?h=gnome-3-6&id=a5a0f6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
adapted from:
https://git.gnome.org/browse/totem/commit/?id=c6fc9c4785904cda4b648dbdbd24958d1010c4a1
https://github.com/linuxmint/xreader/commit/feca69fe519d4c24457d17c0287704aa47688e22
https://github.com/linuxmint/xreader/commit/af897180ec8fb30afb2f96dab23a2f2ae022f087
|
|
taken from:
https://git.gnome.org/browse/totem/commit/?id=07e11de11a9f84209b31ebffdeec4983f91b9dae
https://git.gnome.org/browse/totem/commit/?id=f4eed1f68d3b4ca37c2e7440be37aeaef882a0d5
|
|
from
https://git.gnome.org/browse/totem/commit/?id=3b33d7bd88e9e69c7d45238f7f7e1027aa59ee88
|
|
|
|
as of https://github.com/mate-desktop/eom/commit/8615744bde57e487ab2a662811929b889499f4fd
|
|
|
|
|
|
|
|
it can be made more detailed of course, but for now it will do.
closes https://github.com/mate-desktop/atril/issues/120
|
|
|
|
|
|
|
|
closes https://github.com/mate-desktop/atril/issues/182
|
|
|
|
Once epub support has been implemented, atril crashes with all epubs.
Backtrace for 1.10.2+repack1-1 (Debian Stretch):
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd26d2700 (LWP 22276)]
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ()
#1 0x00007ffff755914e in ev_job_page_data_run (job=0x9e3850 [EvJobPageData]) at ev-jobs.c:762
#2 0x00007ffff755a85a in ev_job_thread_proxy (job=0x9e3850 [EvJobPageData]) at ev-job-scheduler.c:184
#3 0x00007ffff755a85a in ev_job_thread_proxy (data=<optimized out>) at ev-job-scheduler.c:217
#4 0x00007ffff14e1955 in g_thread_proxy (data=0x7fff84002280) at /build/glib2.0-VKSJTv/glib2.0-2.46.1/./glib/gthread.c:778
#5 0x00007ffff08690a4 in start_thread (arg=0x7fffd26d2700) at pthread_create.c:309
#6 0x00007ffff059e06d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb)
It turns out it couldn't really work since one function pointer is
uninitialized. But nobody complained. Thus I investigated it further,
why it fails only for me. First, I tried a gtk3 version. And it works
properly, but the broken code is not hit at all. Due to the threaded
design, it was harder to figure out, why. Here is the code path:
-->
ev_window_load_job_cb (shell/ev-window.c) -->
ev_document_model_set_document (libview/ev-document-model.c) -->
ev_view_document_changed_cb (libview/ev-view.c) -->
setup_caches (libview/ev-view.c) -->
if (ev_view_is_a11y_enabled (view)) {
ev_page_cache_set_flags();
}
ev_page_cache_set_flags (libview/ev-page-cache.c) -->
ev_page_cache_set_page_range (libview/ev-page-cache.c) -->
data->job = ev_job_page_data_new (cache->document, i, flags);
...
ev_job_scheduler_push_job (data->job, EV_JOB_PRIORITY_NONE);
...
-->
ev_job_thread_proxy (libview/ev-job-scheduler.c) -->
ev_job_page_data_run (libview/ev-jobs.c) -->
ev_document_links_get_links (libdocument/ev-document-links.c) -->
EvDocumentLinksInterface *iface = EV_DOCUMENT_LINKS_GET_IFACE (document_links);
return iface->get_links (document_links, page);
(get_links == NULL) --> crash
As one can see it depends on the accessibility. And it is enabled on my
box.
It can be reproduced with
gsettings set org.mate.interface accessibility true
(mate logout and login)
Why the enabled accessibility is not discovered by the gtk3 version is
another story. My question [1] was motivated by this.
[1] https://github.com/mate-desktop/atril/issues/171
|
|
from
https://git.gnome.org/browse/evince/commit/?id=b736348acea926817f25273cf94001a7ef5d547f
|
|
from
https://git.gnome.org/browse/evince/commit?id=397f67d960dc516619ab11be88455de91695eb5c
|
|
from
https://git.gnome.org/browse/evince/commit/?id=28f8be70a6a8c941ef8326cf831238365eae4689
|