Bug 609367

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

architecture: i686
Attached file: backtrace
cmdline: lxpanel --profile LXDE
comment: I don't know what happened.
component: lxpanel
crash_function: on_stretch_render
executable: /usr/bin/lxpanel
global_uuid: 5d4e18045599c346afb61dad0b4a485c72560fbb
kernel: 2.6.33.5-124.fc13.i686
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)
Comment 1 mark.mrwizard 2010-06-30 05:56:03 UTC 
Created attachment 427864 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-07-16 13:23:44 UTC 
Thanks for your bug report. I forwarded upstream as https://sourceforge.net/tracker/?func=detail&aid=3030540&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.