Bug 622482 - [abrt] crash in lxpanel-0.5.5-3.fc13: task_draw_label: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in lxpanel-0.5.5-3.fc13: task_draw_label: Process /usr/bin/lxpan...
Keywords:
Status: CLOSED DUPLICATE of bug 601747
Alias: None
Product: Fedora
Classification: Fedora
Component: lxpanel
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6d764b89f79253887dd3fdd4150...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-09 13:45 UTC by marc
Modified: 2010-08-09 14:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-09 14:17:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (10.17 KB, text/plain)
2010-08-09 13:45 UTC, marc 		no flags Details
View All

Description marc 2010-08-09 13:45:06 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: lxpanel --profile LXDE
component: lxpanel
crash_function: task_draw_label
executable: /usr/bin/lxpanel
global_uuid: 6d764b89f79253887dd3fdd415091c06dce8e6a1
kernel: 2.6.33.5-124.fc13.i686.PAE
package: lxpanel-0.5.5-3.fc13
rating: 4
reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 marc 2010-08-09 13:45:08 UTC 
Created attachment 437598 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-08-09 14:17:22 UTC 
Thanks for reporting this crash. Whenever you file a bug please be so kind as to fill out all fields, especially the comment field and the steps that lead to the crash.

Yu already filed the same crash as bug 609999 which was closed as a duplicate of bug 601747. Instead of reporting the same bug again it is much more helpful if you give me feedback about lxpanel 0.5.6 at https://admin.fedoraproject.org/updates/lxpanel-0.5.6-1.fc13

*** This bug has been marked as a duplicate of bug 601747 ***
Note You need to log in before you can comment on or make changes to this bug.