Bug 669837

Summary: [abrt] lxpanel-0.5.6-1.fc14: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kiran K Telukunta <kiran.telukunta>
Component: lxpanelAssignee: Christoph Wickert <cwickert>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: cwickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:e109419afb2e4c87d3cb57240dfbbc78e686a760
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-09 22:01:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
Stack trace of lxpanel crash none

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.