Bug 595242 - [abrt] crash in gnome-panel-2.28.0-16.fc12: wncklet_connect_while_alive: Process /usr/libexec/wnck-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-panel-2.28.0-16.fc12: wncklet_connect_while_alive: Proc...
Keywords:
Status: CLOSED DUPLICATE of bug 552423
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9de77efe17b20431f2611c11252...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-24 07:53 UTC by Mike Young
Modified: 2010-05-25 09:38 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (14.83 KB, text/plain)
2010-05-24 07:53 UTC, Mike Young 		no flags Details
View All

Description Mike Young 2010-05-24 07:53:50 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=18
comment: don't know..   came back to computer after screensaver activated, window switcher icons had no names, and were grayed out.
component: gnome-panel
crash_function: wncklet_connect_while_alive
executable: /usr/libexec/wnck-applet
global_uuid: 9de77efe17b20431f2611c11252f688bdf5a9e39
kernel: 2.6.32.12-115.fc12.i686
package: gnome-panel-2.28.0-16.fc12
rating: 4
reason: Process /usr/libexec/wnck-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Mike Young 2010-05-24 07:53:53 UTC 
Created attachment 416046 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:38:24 UTC 

*** This bug has been marked as a duplicate of bug 552423 ***
Comment 3 Karel Klíč 2010-05-25 09:38:24 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.