Bug 704871

Summary: [abrt] lxpanel-0.5.6-1.fc14: __i686.get_pc_thunk.bx: Process /usr/bin/lxpanel was killed by signal 4 (SIGILL)
Product: [Fedora] Fedora Reporter: yamil dib <yamil.dib>
Component: lxpanelAssignee: Christoph Wickert <cwickert>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: cwickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:eb2a7bcceaed852f59cd5ab07fa74c0e9c84911a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-03 23:27:30 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

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.