Bug 669837 - [abrt] lxpanel-0.5.6-1.fc14: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Summary: [abrt] lxpanel-0.5.6-1.fc14: Process /usr/bin/lxpanel was killed by signal 11...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lxpanel
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e109419afb2e4c87d3cb57240df...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-14 23:01 UTC by Kiran K Telukunta
Modified: 2011-12-09 22:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-09 22:01:23 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (14.70 KB, text/plain)
2011-01-14 23:01 UTC, Kiran K Telukunta
no flags Details
Stack trace of lxpanel crash (7.87 KB, text/plain)
2011-03-11 00:35 UTC, Sam Shrum
no flags Details

Description Kiran K Telukunta 2011-01-14 23:01:24 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: lxpanel --profile LXDE
component: lxpanel
executable: /usr/bin/lxpanel
kernel: 2.6.35.10-74.fc14.i686
package: lxpanel-0.5.6-1.fc14
rating: 3
reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295045950
uid: 500

How to reproduce
-----
1.
2.
3.asd
a

Comment 1 Kiran K Telukunta 2011-01-14 23:01:28 UTC
Created attachment 473612 [details]
File: backtrace

Comment 2 Christoph Wickert 2011-01-15 10:07:30 UTC
(In reply to comment #0)
> How to reproduce
> -----
> 1.
> 2.
> 3.asd
> a

I'm sorry, but this is not really a helpful description. Was this a random crash or can you reproduce it reliably?

Comment 3 Christoph Wickert 2011-03-06 13:55:14 UTC
Any news here? Without more information there is not much I can do.

Comment 4 Sam Shrum 2011-03-11 00:35:40 UTC
Created attachment 483619 [details]
Stack trace of lxpanel crash

I'm running Fedora 14 on the LXDE spin; install is fresh and only a few hours old. Fully up to date via yum update, with a reboot in the intervening time. LXPanel came up as having a crash, but continued running (seemingly) normally. Seems to be a minor issue at worst.

Comment 5 Christoph Wickert 2011-05-16 08:55:48 UTC
Sorry for the late response.

Sam, you are having a different problem than the original reporter of this bug. Yours is the one from bug 587430. It was already reported to the developers but has never been dealt with. Unfortunately Marty has left LXDE and lxpanel is unmaintained.

Kiran, any news? If I do not hear back from you I will close this bug in 2 weeks from now.

Comment 6 Christoph Wickert 2011-12-09 22:01:23 UTC
As I have not heard back from the reporter and the backtrace lacks debugsymbols there is nothing I can do here.


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