Bug 684613 - [abrt] lxpanel-0.5.6-1.fc14: taskbar_task_control_event: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Summary: [abrt] lxpanel-0.5.6-1.fc14: taskbar_task_control_event: Process /usr/bin/lxp...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lxpanel
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6b2f23c64ac1515cab869a43388...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-13 20:36 UTC by Jeremy Baudoin
Modified: 2011-05-16 17:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-16 17:21:14 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (24.57 KB, text/plain)
2011-03-13 20:36 UTC, Jeremy Baudoin
no flags Details

Description Jeremy Baudoin 2011-03-13 20:36:42 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 25156 bytes
cmdline: lxpanel --profile LXDE
component: lxpanel
Attached file: coredump, 8900608 bytes
crash_function: taskbar_task_control_event
executable: /usr/bin/lxpanel
kernel: 2.6.35.11-83.fc14.x86_64
package: lxpanel-0.5.6-1.fc14
rating: 4
reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300048095
uid: 500

How to reproduce
-----
1.
2.
3.
use skype

Comment 1 Jeremy Baudoin 2011-03-13 20:36:44 UTC
Created attachment 484047 [details]
File: backtrace

Comment 2 Christoph Wickert 2011-03-13 20:56:26 UTC
Can you give me more details about the crash? Does lxpanel crash every time you use skype? What exactly did you do when it crashed?

Comment 3 Christoph Wickert 2011-03-28 00:41:37 UTC
Jeremy, any news here?

Comment 4 Christoph Wickert 2011-05-16 17:21:14 UTC
No reply, no fix, sorry.

Feel free to reopen this bug if you can provide the info I need for further investigation. Thanks!


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