Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 589982 - [abrt] crash in lxpanel-0.5.5-3.fc12: IA__gtk_widget_destroy: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in lxpanel-0.5.5-3.fc12: IA__gtk_widget_destroy: Process /usr/bi...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: lxpanel
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL: https://sourceforge.net/tracker/?func...
Whiteboard: abrt_hash:d57cdfee8de6e61ed6fdfaf8094...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-07 13:01 UTC by Matěj Pakosta
Modified: 2010-07-16 12:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-16 12:44:52 UTC


Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-07 13:01 UTC, Matěj Pakosta
no flags Details

Description Matěj Pakosta 2010-05-07 13:01:33 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: lxpanel --profile LXDE
component: lxpanel
crash_function: IA__gtk_widget_destroy
executable: /usr/bin/lxpanel
global_uuid: d57cdfee8de6e61ed6fdfaf80947524af9929290
kernel: 2.6.32.11-99.fc12.x86_64
package: lxpanel-0.5.5-3.fc12
rating: 4
reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Matěj Pakosta 2010-05-07 13:01:37 UTC
Created attachment 412344 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-07-16 12:44:52 UTC
Thanks for your bug report. I forwarded upstream as https://sourceforge.net/tracker/?func=detail&aid=3030521&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.


Note You need to log in before you can comment on or make changes to this bug.