Bug 587970

Summary: [abrt] crash in lxpanel-0.5.5-3.fc13: Process /usr/bin/lxpanel was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: amit
Component: lxpanelAssignee: Christoph Wickert <cwickert>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: amorilia, cwickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: https://sourceforge.net/tracker/?func=detail&aid=3030511&group_id=180858&atid=894869
Whiteboard: abrt_hash:73d820b95f1fc9e944375e22552b2c2c558d8c78
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-16 12:26:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
File: backtrace none

Description amit 2010-05-01 21:52:21 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: lxpanel --profile LXDE
component: lxpanel
executable: /usr/bin/lxpanel
global_uuid: 73d820b95f1fc9e944375e22552b2c2c558d8c78
package: lxpanel-0.5.5-3.fc13
rating: 4
reason: Process /usr/bin/lxpanel was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1. Login with LXDE session
2. Right click on panel and click 'Add/Remove panel items...'
3. Click 'Add'
4. Select 'Network Status Monitor' and then click 'Add'
5. lxpanel crashed
Could not reproduce it after panel crashed once. Second time, the network status item was added successfully.

Comment 1 amit 2010-05-01 21:52:24 UTC
Created attachment 410733 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-07-16 12:26:56 UTC
Thanks for your bug report. I 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.

Comment 3 Christoph Wickert 2010-07-16 13:00:41 UTC
*** Bug 600831 has been marked as a duplicate of this bug. ***