Description of problem: I had print dialog opened for longer time (like 15-30 minutes) and then moved both windows via window manager (default in gnome shell) and program crashed during windows movement. Version-Release number of selected component: evince-3.14.2-5.el7 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: evince /home/dkutalek/Downloads/20160418_potvrzeni.pdf crash_function: g_wakeup_new executable: /usr/bin/evince global_pid: 14743 kernel: 3.10.0-327.13.1.el7.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 9 (10 frames) #2 g_wakeup_new at /lib64/libglib-2.0.so.0 #3 g_main_context_new at /lib64/libglib-2.0.so.0 #4 g_dbus_connection_send_message_with_reply_sync at /lib64/libgio-2.0.so.0 #5 g_dbus_connection_call_sync_internal at /lib64/libgio-2.0.so.0 #6 g_dbus_proxy_call_sync_internal at /lib64/libgio-2.0.so.0 #7 g_dbus_proxy_call_sync at /lib64/libgio-2.0.so.0 #8 gvfs_metadata_call_set_sync at /usr/lib64/gio/modules/libgvfsdbus.so #9 g_daemon_vfs_local_file_set_attributes at /usr/lib64/gio/modules/libgvfsdbus.so #10 _g_local_file_info_set_attributes at /lib64/libgio-2.0.so.0 #11 g_local_file_set_attributes_from_info at /lib64/libgio-2.0.so.0
Created attachment 1148143 [details] File: backtrace
Created attachment 1148144 [details] File: cgroup
Created attachment 1148145 [details] File: core_backtrace
Created attachment 1148146 [details] File: dso_list
Created attachment 1148147 [details] File: environ
Created attachment 1148148 [details] File: limits
Created attachment 1148149 [details] File: machineid
Created attachment 1148150 [details] File: maps
Created attachment 1148151 [details] File: open_fds
Created attachment 1148152 [details] File: proc_pid_status
Created attachment 1148153 [details] File: var_log_messages
Created attachment 1148154 [details] File: sosreport.tar.xz
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.