Version-Release number of selected component: xfce4-panel-4.10.1-3.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: xfce4-panel --display :0.0 --sm-client-id 20bab7453-04c1-4a8a-b971-33d16c7a8f42 crash_function: launcher_clicked executable: /usr/bin/xfce4-panel kernel: 3.12.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 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
Created attachment 855376 [details] File: backtrace
Created attachment 855377 [details] File: cgroup
Created attachment 855378 [details] File: core_backtrace
Created attachment 855379 [details] File: dso_list
Created attachment 855380 [details] File: environ
Created attachment 855381 [details] File: exploitable
Created attachment 855382 [details] File: limits
Created attachment 855383 [details] File: maps
Created attachment 855384 [details] File: open_fds
Created attachment 855385 [details] File: proc_pid_status
Created attachment 855386 [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? I think I found it in the abrt logs shortly after waking up my laptop from sleep. > Can you duplicate it? probably not, I'll keep my eyes open if it happens again.
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.