Version-Release number of selected component: xfce4-panel-4.10.1-6.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper /usr/lib64/xfce4/panel/plugins/libsystemload.so 34 25165876 systemload 'System Load Monitor' 'Monitor CPU load, swap usage and memory footprint' '' crash_function: monitor_free executable: /usr/lib64/xfce4/panel/wrapper kernel: 3.17.4-301.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #7 monitor_free at systemload.c:397 #8 _g_closure_invoke_va at gclosure.c:831 #11 xfce_panel_plugin_dispose at xfce-panel-plugin.c:907 #13 gtk_container_destroy at gtkcontainer.c:1073 #18 gtk_object_dispose at gtkobject.c:421
Created attachment 966648 [details] File: backtrace
Created attachment 966649 [details] File: cgroup
Created attachment 966651 [details] File: core_backtrace
Created attachment 966652 [details] File: dso_list
Created attachment 966653 [details] File: environ
Created attachment 966654 [details] File: limits
Created attachment 966656 [details] File: maps
Created attachment 966657 [details] File: open_fds
Created attachment 966658 [details] File: proc_pid_status
Created attachment 966659 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate the crash?
(In reply to Kevin Fenzi from comment #11) > What were you doing when this happened? I was logging out from xfce. > Can you duplicate the crash? No idea.
(In reply to Ralf Corsepius from comment #12) > (In reply to Kevin Fenzi from comment #11) > > What were you doing when this happened? > I was logging out from xfce. > > > Can you duplicate the crash? > No idea. Same here ...(I was logging out from xfce).
Same here ...I was logging out from xfce, and log back.... If you want to duplicate the crash, just logging out and log back.
Another user experienced a similar problem: No idea, just got the notification about the crash. Possibly from reading from an old config?! reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper /usr/lib64/xfce4/panel/plugins/libsystemload.so 24 23068714 systemload 'System Load Monitor' 'Monitor CPU load, swap usage and memory footprint' '' crash_function: monitor_free executable: /usr/lib64/xfce4/panel/wrapper kernel: 3.18.9-200.fc21.x86_64 package: xfce4-panel-4.10.1-6.fc21 reason: wrapper killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.