Bug 605995 - [abrt] crash in lxpanel-0.5.5-3.fc13: delay_update_background. Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in lxpanel-0.5.5-3.fc13: delay_update_background. Process /usr/b...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: lxpanel
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL: https://sourceforge.net/tracker/?func...
Whiteboard: abrt_hash:7cf83eaa0b137593be6aad134cf...
: 615103 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-19 20:44 UTC by Ryan
Modified: 2010-07-16 13:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-16 13:50:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (17.50 KB, text/plain)
2010-06-19 20:44 UTC, Ryan 		no flags Details
View All

Description Ryan 2010-06-19 20:44:33 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: lxpanel --profile LXDE
comment: Happens upon basic startup
component: lxpanel
crash_function: IA__g_type_check_instance_cast
executable: /usr/bin/lxpanel
global_uuid: 7cf83eaa0b137593be6aad134cf2b4a83a45088e
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)

How to reproduce
-----
1.Startup
2.
3.
Comment 1 Ryan 2010-06-19 20:44:34 UTC 
Created attachment 425381 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-07-16 13:50:22 UTC 
Thanks for your bug report. I forwarded upstream as https://sourceforge.net/tracker/?func=detail&aid=3030553&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:53:34 UTC 
*** Bug 615103 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.