Bug 621868 - [abrt] crash in lxpanel-0.5.5-3.fc13: IA__gtk_widget_set_tooltip_text: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in lxpanel-0.5.5-3.fc13: IA__gtk_widget_set_tooltip_text: Proces...
Keywords:
Status: CLOSED DUPLICATE of bug 643644
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:8badcc119e12d6a88b44273ed0a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-06 10:42 UTC by Terry Wallwork
Modified: 2012-06-10 18:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-10 10:23:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (8.33 KB, text/plain)
2010-08-06 10:42 UTC, Terry Wallwork
no flags Details

Description Terry Wallwork 2010-08-06 10:42:01 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: lxpanel --profile LXDE
comment: closing my archive manager (i think), not sure.
component: lxpanel
crash_function: IA__gtk_widget_set_tooltip_text
executable: /usr/bin/lxpanel
global_uuid: 8badcc119e12d6a88b44273ed0a691fe94ac13ed
kernel: 2.6.33.6-147.fc13.i686
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 Terry Wallwork 2010-08-06 10:42:04 UTC
Created attachment 437108 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-08-10 10:22:36 UTC
This looks like a duplicate of bug 587430 to me and I'm very optimistic that it is fixed with lxpanel 0.5.6. Can you please test the update and provide feedbac at https://admin.fedoraproject.org/updates/lxpanel-0.5.6-1.fc13

Comment 3 Christoph Wickert 2010-08-10 10:23:28 UTC

*** This bug has been marked as a duplicate of bug 587430 ***

Comment 4 Christoph Wickert 2012-06-10 18:37:05 UTC

*** This bug has been marked as a duplicate of bug 643644 ***


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