Bug 617377 - [abrt] lxpanel-0.5.5-3.fc14: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
[abrt] lxpanel-0.5.5-3.fc14: Process /usr/bin/lxpanel was killed by signal 11...
Product: Fedora
Classification: Fedora
Component: lxpanel (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Christoph Wickert
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-22 17:17 EDT by Karsten Roch
Modified: 2010-07-22 18:04 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-22 18:04:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (5.47 KB, text/plain)
2010-07-22 17:17 EDT, Karsten Roch
no flags Details

  None (edit)
Description Karsten Roch 2010-07-22 17:17:54 EDT
abrt version: 1.1.5
architecture: i686
Attached file: backtrace
cmdline: lxpanel --profile LXDE
component: lxpanel
executable: /usr/bin/lxpanel
global_uuid: fa5d0ce7ac3fc6a47b77ba239a59e6f5a59f48ef
kernel: 2.6.35-0.49.rc5.git2.fc14.i686
package: lxpanel-0.5.5-3.fc14
rating: 3
reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Rawhide)
time: 1279833319
uid: 500

How to reproduce
1. Closing firefox 3.6.4, but download-window of firefox was still open 
2.lx-panel crash
Comment 1 Karsten Roch 2010-07-22 17:17:56 EDT
Created attachment 433809 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-07-22 18:04:55 EDT
I'm pretty sure this is a duplicate of one of the many lxpanel bugs I have, but I don't find the original ATM because the backtrace lacks the debuginfo of lxpanel. If you can repproduce this crash reliably, please run

  debuginfo-install lxpanel 
before you let ABRT generate the backtrace

With this backtrace there is not much I can do, but I'm optimistic that it's one of the crashers that are fixed in 0.5.6, which is going to come soon.

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