abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/libexec/xfce4/panel-plugins/xfce4-sensors-plugin socket_id 29360174 name xfce4-sensors-plugin id 12762278041 display_name 'Sensor plugin' size 25 screen_position 2 component: xfce4-sensors-plugin crash_function: malloc_consolidate executable: /usr/libexec/xfce4/panel-plugins/xfce4-sensors-plugin global_uuid: 48d50d04a052e05f02a44c4c5a66603c9f52f228 kernel: 2.6.33.5-124.fc13.i686.PAE package: xfce4-sensors-plugin-1.0.0-1.fc13 rating: 4 reason: Process /usr/libexec/xfce4/panel-plugins/xfce4-sensors-plugin was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1. I have no idea how or when this crashed. Sorry. 2. 3.
Created attachment 426065 [details] File: backtrace
*** Bug 611057 has been marked as a duplicate of this bug. ***
*** Bug 611058 has been marked as a duplicate of this bug. ***
Forwarded upstream as http://bugzilla.xfce.org/show_bug.cgi?id=6541
I'm now closing the bug UPSTREAM because this is where further investigation should take place. Feel free to add yourself to the upstream bug report in order to follow any changes. Even if you don't, will be notified once this bug is resolved in Fedora. If I need more information, I will get back to you. Thanks for reporting this bug.
*** Bug 630447 has been marked as a duplicate of this bug. ***
*** Bug 636332 has been marked as a duplicate of this bug. ***
Christoph, FYI This bug seems to occur currently again more often. I think it has something to do with a recent update to one or more Fedora packages, but do not ask me which ones exactly. I encountered a crash of the plugin by myself recently, but I did not check the report against duplication.
*** Bug 643084 has been marked as a duplicate of this bug. ***
*** Bug 651118 has been marked as a duplicate of this bug. ***
Also related to Fedora14. See therefore some duplications of this bug.
*** Bug 654307 has been marked as a duplicate of this bug. ***
*** Bug 659504 has been marked as a duplicate of this bug. ***