Bug 690312 - [abrt] lxpanel-0.5.6-2.fc15: _XAllocID: Process /usr/bin/lxpanel was killed by signal 6 (SIGABRT)
Summary: [abrt] lxpanel-0.5.6-2.fc15: _XAllocID: Process /usr/bin/lxpanel was killed b...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lxpanel
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5236ce20e4e9fd3d428a8e7406f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-23 20:50 UTC by jimmy
Modified: 2011-03-28 00:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-28 00:46:37 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (20.40 KB, text/plain)
2011-03-23 20:50 UTC, jimmy
no flags Details

Description jimmy 2011-03-23 20:50:30 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 20886 bytes
cmdline: lxpanel --profile LXDE
component: lxpanel
Attached file: coredump, 29630464 bytes
crash_function: _XAllocID
executable: /usr/bin/lxpanel
kernel: 2.6.38-1.fc15.i686
package: lxpanel-0.5.6-2.fc15
rating: 3
reason: Process /usr/bin/lxpanel was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
How to reproduce: I have a fresh install of the Alpha running for testing/peek-lloking on my ASUS EEEPC 1000H with stock equipment. Sorry for not being able to give more details. I run look around in the release and check things out.
time: 1300911293
uid: 500

Comment 1 jimmy 2011-03-23 20:50:33 UTC
Created attachment 487145 [details]
File: backtrace

Comment 2 Christoph Wickert 2011-03-25 11:44:18 UTC
Was this a random crash or does it happen every time? What did you do when the panel crashed? Just booted?

Comment 3 jimmy 2011-03-25 12:54:42 UTC
I have just spent 20 minutes trying to reproduce the problem without success. I'd say random crasch. Didn't do anything when it crasched that one time on the 23:d. Just booted and logged in. Can there be a significant difference if I have setup automatic login or not?

Comment 4 Christoph Wickert 2011-03-25 13:01:10 UTC
Nope, it's just random and these things are hard to troubleshoot. :(

Comment 5 Christoph Wickert 2011-03-28 00:46:37 UTC
I just realized that the backtrace lacks debug symbols of GTK+2 which renders it pretty much useless. Can you please run

debuginfo-install gtk2

and submit a new bug report when the panel crashes again? Thanks, I'm sorry I can't do more for you ATM.


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