Bug 659504

Summary: [abrt] xfce4-sensors-plugin-1.0.0-1.fc14: malloc_consolidate: Process /usr/libexec/xfce4/panel-plugins/xfce4-sensors-plugin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: igor.redhat <igor.redhat>
Component: xfce4-sensors-pluginAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:606d08edcb6165b2617cf44835ca36484e93ad63
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-02 22:46:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description igor.redhat@gmail.com 2010-12-02 22:30:51 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/xfce4/panel-plugins/xfce4-sensors-plugin socket_id 20971570 name xfce4-sensors-plugin id 12865789133 display_name 'Sensor plugin' size 19 screen_position 13
component: xfce4-sensors-plugin
crash_function: malloc_consolidate
executable: /usr/libexec/xfce4/panel-plugins/xfce4-sensors-plugin
kernel: 2.6.35.6-48.fc14.x86_64
package: xfce4-sensors-plugin-1.0.0-1.fc14
rating: 4
reason: Process /usr/libexec/xfce4/panel-plugins/xfce4-sensors-plugin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1291328904
uid: 500

How to reproduce
-----
The crash happened when restarting the Panel. It doesn't seem to be easily reproducible
Comment 1 igor.redhat@gmail.com 2010-12-02 22:30:53 UTC 
Created attachment 464395 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-12-02 22:46:14 UTC 
This a duplicate. ABRT failed to detect it because glibc-debuginfo is not present.

*** This bug has been marked as a duplicate of bug 606958 ***