Description of problem: logged in Xfce (rawhide) Version-Release number of selected component: xfce4-panel-4.10.1-1.fc20 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper /usr/lib64/xfce4/panel/plugins/libsystray.so 6 12582945 systray 'Notification Area' 'Area where notification icons appear' '' crash_function: handle_error executable: /usr/lib64/xfce4/panel/wrapper kernel: 3.11.0-0.rc1.git1.1.fc20.x86_64 runlevel: N 5 uid: 1005 Truncated backtrace: Thread no. 1 (10 frames) #4 handle_error at xcb_io.c:213 #5 handle_response at xcb_io.c:325 #7 XInternAtom at IntAtom.c:181 #8 gdk_x11_atom_to_xatom_for_display at gdkproperty-x11.c:210 #9 _gtk_xembed_send_message at gtkxembed.c:157 #10 _gtk_socket_windowing_embed_notify at gtksocket-x11.c:286 #11 _gtk_socket_add_window at gtksocket.c:954 #12 gtk_socket_add_id at gtksocket.c:346 #13 systray_manager_handle_dock_request at systray-manager.c:713 #14 systray_manager_window_filter at systray-manager.c:494 Potential duplicate: bug 712779
Created attachment 776479 [details] File: backtrace
Created attachment 776480 [details] File: cgroup
Created attachment 776481 [details] File: core_backtrace
Created attachment 776482 [details] File: dso_list
Created attachment 776483 [details] File: environ
Created attachment 776484 [details] File: limits
Created attachment 776485 [details] File: maps
Created attachment 776486 [details] File: open_fds
Created attachment 776487 [details] File: proc_pid_status
Created attachment 776488 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
Hi Kevin, it happened while I was log in my Xfce desktop. For while it happened once, but I've decided to report it since it happened in rawhide. Let me know if you need additional debug from my side.
ok. I'll see what I can make of the backtrace. Thanks for reporting.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
Another user experienced a similar problem: The problem appeared just right after I logged in. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper /usr/lib64/xfce4/panel/plugins/libsystray.so 6 25165871 systray 'Notification Area' 'Area where notification icons appear' '' crash_function: handle_error executable: /usr/lib64/xfce4/panel/wrapper kernel: 3.14.4-200.fc20.x86_64 package: xfce4-panel-4.10.1-3.fc20 reason: wrapper killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: The environment crashed after rebooting in the middle of an update. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper /usr/lib64/xfce4/panel/plugins/libsystray.so 6 25165857 systray 'Notification Area' 'Area where notification icons appear' '' crash_function: handle_error executable: /usr/lib64/xfce4/panel/wrapper kernel: 3.13.5-202.fc20.x86_64 package: xfce4-panel-4.10.1-3.fc20 reason: wrapper killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: During the startup of the Xfce desktop ! reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper /usr/lib64/xfce4/panel/plugins/libsystray.so 5 25165870 systray 'Notification Area' 'Area where notification icons appear' '' crash_function: handle_error executable: /usr/lib64/xfce4/panel/wrapper kernel: 3.14.8-200.fc20.x86_64 package: xfce4-panel-4.10.1-3.fc20 reason: wrapper killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Don't know. Just logged in XFCE. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper /usr/lib64/xfce4/panel/plugins/libsystray.so 6 10485796 systray 'Notification Area' 'Area where notification icons appear' '' crash_function: handle_error executable: /usr/lib64/xfce4/panel/wrapper kernel: 3.14.8-200.fc20.x86_64 package: xfce4-panel-4.10.1-3.fc20 reason: wrapper killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: i just started the computer... reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper /usr/lib64/xfce4/panel/plugins/libsystray.so 6 23068705 systray 'Notification Area' 'Area where notification icons appear' '' crash_function: handle_error executable: /usr/lib64/xfce4/panel/wrapper kernel: 3.14.9-200.fc20.x86_64 package: xfce4-panel-4.10.1-3.fc20 reason: wrapper killed by SIGTRAP runlevel: unknown type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.