Description of problem: Accidentially re-opened a document, that was already open (by double-clicking it). I can currently reproduce this in this current session. Version-Release number of selected component: atril-1.12.2-2.fc22 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: atril /home/alexander/Documents/me-td/praktikum/A1_MuTD_SS2016.pdf crash_function: ev_web_view_disconnect_handlers executable: /usr/bin/atril global_pid: 11351 kernel: 4.4.8-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ev_web_view_disconnect_handlers at ev-web-view.c:865 #1 ev_window_set_document at ev-window.c:1599 #2 ev_window_document_changed_cb at ev-window.c:4859 #8 g_object_notify_by_spec_internal at gobject.c:1149 #9 g_object_notify at gobject.c:1197 #10 ev_document_model_set_document at ev-document-model.c:306 #11 ev_window_reload_job_cb at ev-window.c:1833 #12 _g_closure_invoke_va at gclosure.c:831 #15 emit_finished at ev-jobs.c:193 #20 gtk_main at gtkmain.c:1268 Potential duplicate: bug 1333811
Created attachment 1155452 [details] File: backtrace
Created attachment 1155453 [details] File: cgroup
Created attachment 1155454 [details] File: core_backtrace
Created attachment 1155455 [details] File: dso_list
Created attachment 1155456 [details] File: environ
Created attachment 1155457 [details] File: limits
Created attachment 1155458 [details] File: maps
Created attachment 1155459 [details] File: mountinfo
Created attachment 1155460 [details] File: namespaces
Created attachment 1155461 [details] File: open_fds
Created attachment 1155462 [details] File: proc_pid_status
Created attachment 1155463 [details] File: var_log_messages
The upstream commit to fix previous bugreports causes a regression, see https://github.com/mate-desktop/atril/issues/198 https://bugzilla.redhat.com/show_bug.cgi?id=1333811 I will revert the culprit patch, but this will introduce previous issues with firefox again. Main prob is that epub code is involved if using pdfs. Btw. it looks like that webkit code is in general a bit buggy. Sorry for that fallout, we will work at upstream to fix previous issues without introducing a regression again.
*** This bug has been marked as a duplicate of bug 1333811 ***