Version-Release number of selected component: xfce4-panel-4.12.0-3.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper-1.0 /usr/lib64/xfce4/panel/plugins/libsystray.so 6 20971554 systray 'Notification Area' 'Area where notification icons appear' '' crash_function: XInternAtom executable: /usr/lib64/xfce4/panel/wrapper-1.0 global_pid: 3862 kernel: 4.0.8-300.fc22.x86_64+debug runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #8 XInternAtom at IntAtom.c:181 #9 gdk_x11_atom_to_xatom_for_display at gdkproperty-x11.c:210 #10 _gtk_xembed_send_message at gtkxembed.c:157 #11 _gtk_socket_windowing_embed_notify at gtksocket-x11.c:286 #12 _gtk_socket_add_window at gtksocket.c:954 #13 gtk_socket_add_id at gtksocket.c:346 #14 systray_manager_window_filter at systray-manager.c:713 #16 gdk_event_apply_filters at gdkevents-x11.c:371 #17 gdk_event_translate at gdkevents-x11.c:1074 #18 _gdk_events_queue at gdkevents-x11.c:2358 Potential duplicate: bug 1211886
Created attachment 1061070 [details] File: backtrace
Created attachment 1061071 [details] File: cgroup
Created attachment 1061072 [details] File: core_backtrace
Created attachment 1061073 [details] File: dso_list
Created attachment 1061074 [details] File: environ
Created attachment 1061075 [details] File: limits
Created attachment 1061076 [details] File: maps
Created attachment 1061077 [details] File: mountinfo
Created attachment 1061078 [details] File: namespaces
Created attachment 1061079 [details] File: open_fds
Created attachment 1061080 [details] File: proc_pid_status
What were you doing when this happened? Can you duplicate the crash?
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.