Bug 600831

Summary: [abrt] crash in lxpanel-0.5.5-3.fc13: panel_draw_label_text: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: amorilia
Component: lxpanelAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://sourceforge.net/tracker/?func=detail&aid=3030520&group_id=180858&atid=894869
Whiteboard: abrt_hash:df73f1dafaa206bacc83903af6c3c57673ebd18e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-16 13:00:41 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 amorilia 2010-06-06 08:56:35 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: lxpanel --profile LXDE
component: lxpanel
crash_function: panel_draw_label_text
executable: /usr/bin/lxpanel
global_uuid: df73f1dafaa206bacc83903af6c3c57673ebd18e
kernel: 2.6.33.5-112.fc13.x86_64
package: lxpanel-0.5.5-3.fc13
rating: 4
reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.
2.
3.

The segfault just seemed to occur randomly. So far I do not know how to reproduce this reliably.
Comment 1 amorilia 2010-06-06 08:56:38 UTC 
Created attachment 421561 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-07-16 13:00:41 UTC 
Thanks for your bug report. Obviously it is related to bug 587970, which I already forwarded upstream as https://sourceforge.net/tracker/?func=detail&aid=3030511&group_id=180858&atid=894869

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.

I'm now closing the bug UPSTREAM because this is where further investigation should take place.

*** This bug has been marked as a duplicate of bug 587970 ***
Comment 3 Christoph Wickert 2010-07-16 13:08:45 UTC 
Sorry, wrong numbers for the other bug report, the correct one is 587430 and the correct upstream bug report is https://sourceforge.net/tracker/?func=detail&aid=3030520&group_id=180858&atid=894869

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