Version-Release number of selected component: xfce4-panel-4.10.1-3.fc19 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: xfce4-panel --display :0.0 --sm-client-id 24ffc650d-bf4b-41e2-845d-2b79bb1f8b9c crash_function: launcher_clicked executable: /usr/bin/xfce4-panel kernel: 3.13.7-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 launcher_clicked at main.c:471 #1 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #6 gtk_widget_event_internal at gtkwidget.c:5017 #7 gtk_widget_event at gtkwidget.c:4814 #8 gtk_propagate_event at gtkmain.c:2490 #9 gtk_main_do_event at gtkmain.c:1685 #15 gtk_main at gtkmain.c:1257 Potential duplicate: bug 1057859
Created attachment 902709 [details] File: backtrace
Created attachment 902710 [details] File: cgroup
Created attachment 902711 [details] File: core_backtrace
Created attachment 902712 [details] File: dso_list
Created attachment 902713 [details] File: environ
Created attachment 902714 [details] File: exploitable
Created attachment 902715 [details] File: limits
Created attachment 902716 [details] File: maps
Created attachment 902717 [details] File: open_fds
Created attachment 902718 [details] File: proc_pid_status
Created attachment 902719 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
(In reply to Kevin Fenzi from comment #12) > What were you doing when this happened? > > Can you duplicate it? Not sure if that helps, but I had running xchat where I double-left-clicked in a private conversation to some text to mark the word as selected (for future copy and paste). That time, xchat application exited, and abrt reported xfce4-panel SIGSEGV (???). Reporting it, I was directed to this BZ. /me using xfce4-panel-4.10.1-3.fc19, havent reproduced since then.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.