Bug 585616 - [abrt] crash in gnome-panel-2.30.0-1.fc13: Process /usr/libexec/wnck-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-panel-2.30.0-1.fc13: Process /usr/libexec/wnck-applet w...
Keywords:
Status: CLOSED DUPLICATE of bug 552423
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fc5faae82fe7765cf02c04d9119...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-25 04:46 UTC by Anatoli Sakhnik
Modified: 2010-05-25 09:36 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:36:52 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (25.28 KB, text/plain)
2010-04-25 04:46 UTC, Anatoli Sakhnik 		no flags Details
View All

Description Anatoli Sakhnik 2010-04-25 04:46:47 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior-fd=24
comment: Noticed too big desktop switcher applet, right clicked on it, and chose Parameters.
component: gnome-panel
executable: /usr/libexec/wnck-applet
global_uuid: fc5faae82fe7765cf02c04d9119bf7e758987378
kernel: 2.6.33.2-57.fc13.i686
package: gnome-panel-2.30.0-1.fc13
rating: 4
reason: Process /usr/libexec/wnck-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: This was randomly
Comment 1 Anatoli Sakhnik 2010-04-25 04:46:50 UTC 
Created attachment 408917 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:36:52 UTC 

*** This bug has been marked as a duplicate of bug 552423 ***
Comment 3 Karel Klíč 2010-05-25 09:36:52 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #552423.

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