Bug 578984 - [abrt] crash in lxpanel-0.5.5-3.fc12: flash_window_timeout: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in lxpanel-0.5.5-3.fc12: flash_window_timeout: Process /usr/bin/...
Keywords:
Status: CLOSED DUPLICATE of bug 587430
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:
Whiteboard: abrt_hash:08749a009d686e10154171b5b06...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-02 00:44 UTC by Matteo Pasotti
Modified: 2010-10-16 17:53 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-29 22:35:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (7.69 KB, text/plain)
2010-04-02 00:44 UTC, Matteo Pasotti 		no flags Details
View All

Description Matteo Pasotti 2010-04-02 00:44:03 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: lxpanel --profile LXDE
component: lxpanel
executable: /usr/bin/lxpanel
kernel: 2.6.32.9-70.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)

How to reproduce
-----
1. closing firefox window (single)
2. firefox process terminates without prompting for saving tabs
3. lxpanel crash and restart automatically
Comment 1 Matteo Pasotti 2010-04-02 00:44:06 UTC 
Created attachment 404116 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-04-03 17:19:12 UTC 
Thanks for your report. Unfortunately the backtrace lacks a lot of debuginfo, this is a bug in abrt. Please run 
$ debuginfo-install lxpanel
manually, then try to reproduce the crash and submit a new backtrace. TIA!
Comment 3 Christoph Wickert 2010-04-29 22:35:03 UTC 
OK, we have a better backtrace of this crash in bug 587430 now, so I'm closing this one now.

*** This bug has been marked as a duplicate of bug 587430 ***
Note You need to log in before you can comment on or make changes to this bug.