Description of problem: possibly something to do with wayland session? Version-Release number of selected component: gvfs-1.22.1-2.fc22 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-recent --spawner :1.2 /org/gtk/gvfs/exec_spaw/3 crash_function: _gdk_wayland_display_queue_events executable: /usr/libexec/gvfsd-recent kernel: 3.18.0-0.rc1.git4.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #2 _gdk_wayland_display_queue_events at gdkeventsource.c:163 #3 gdk_display_get_event at gdkdisplay.c:321 #9 daemon_main at daemon-main.c:405
Created attachment 951667 [details] File: backtrace
Created attachment 951668 [details] File: cgroup
Created attachment 951669 [details] File: core_backtrace
Created attachment 951670 [details] File: dso_list
Created attachment 951671 [details] File: environ
Created attachment 951672 [details] File: limits
Created attachment 951673 [details] File: maps
Created attachment 951674 [details] File: open_fds
Created attachment 951675 [details] File: proc_pid_status
Created attachment 951676 [details] File: var_log_messages
It seems to me it is bug in gdk since there is several similar bug reports from different packages, see also: https://bugzilla.redhat.com/buglist.cgi?quicksearch=_gdk_wayland_display_queue_events&list_id=2964762
*** Bug 1159992 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.