Description of problem: I do not know what caused this problem. Version-Release number of selected component: xfce4-notifyd-0.2.4-4.fc22 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/notifyd/xfce4-notifyd crash_function: gdk_x_error executable: /usr/lib64/xfce4/notifyd/xfce4-notifyd kernel: 3.17.0-0.rc1.git3.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 gdk_x_error at /lib64/libgdk-x11-2.0.so.0 #3 _XError at /lib64/libX11.so.6 #4 handle_error at /lib64/libX11.so.6 #5 handle_response at /lib64/libX11.so.6 #6 _XEventsQueued at /lib64/libX11.so.6 #7 XPending at /lib64/libX11.so.6 #8 gdk_event_check at /lib64/libgdk-x11-2.0.so.0 #9 g_main_context_check at /lib64/libglib-2.0.so.0 #10 g_main_context_iterate.isra at /lib64/libglib-2.0.so.0 #12 gtk_main at /lib64/libgtk-x11-2.0.so.0
Created attachment 930615 [details] File: backtrace
Created attachment 930616 [details] File: cgroup
Created attachment 930617 [details] File: core_backtrace
Created attachment 930618 [details] File: dso_list
Created attachment 930619 [details] File: environ
Created attachment 930620 [details] File: limits
Created attachment 930621 [details] File: maps
Created attachment 930622 [details] File: open_fds
Created attachment 930623 [details] File: proc_pid_status
Created attachment 930624 [details] File: var_log_messages
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.