Bug 704871 - [abrt] lxpanel-0.5.6-1.fc14: __i686.get_pc_thunk.bx: Process /usr/bin/lxpanel was killed by signal 4 (SIGILL)
Summary: [abrt] lxpanel-0.5.6-1.fc14: __i686.get_pc_thunk.bx: Process /usr/bin/lxpanel...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lxpanel
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:eb2a7bcceaed852f59cd5ab07fa...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-15 15:19 UTC by yamil dib
Modified: 2012-03-03 23:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-03 23:27:30 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (16.24 KB, text/plain)
2011-05-15 15:19 UTC, yamil dib 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description yamil dib 2011-05-15 15:19:30 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: lxpanel --profile LXDE
component: lxpanel
crash_function: __i686.get_pc_thunk.bx
executable: /usr/bin/lxpanel
kernel: 2.6.35.6-45.fc14.i686
package: lxpanel-0.5.6-1.fc14
rating: 4
reason: Process /usr/bin/lxpanel was killed by signal 4 (SIGILL)
release: Fedora release 14 (Laughlin)
time: 1305470476
uid: 500
Comment 1 yamil dib 2011-05-15 15:19:33 UTC 
Created attachment 499025 [details]
File: backtrace
Comment 2 Christoph Wickert 2011-05-16 08:49:14 UTC 
What did you do when the panel crashed? Can your reproduce the crash reliably? If so, how?
Comment 3 Christoph Wickert 2011-06-02 19:43:47 UTC 
Yamil, can you please reply to my questions?
Comment 4 Christoph Wickert 2011-06-17 21:59:53 UTC 
Yamil, this is my third and last attempt to get more info from you. If you do not respond I'll have to close this bug.
Comment 5 Christoph Wickert 2012-03-03 23:27:30 UTC 
Feel free tp reopen this bug once you can provide more info.
Note You need to log in before you can comment on or make changes to this bug.