Bug 605250 - [abrt] crash in gnome-panel-2.30.0-1.fc13: wncklet_connect_while_alive: Process /usr/libexec/wnck-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-panel-2.30.0-1.fc13: wncklet_connect_while_alive: Proce...
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:d072d5918b34f7ad13dfdb2af49...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-17 14:08 UTC by stevieschafer
Modified: 2010-06-21 18:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-21 18:02:39 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (24.55 KB, text/plain)
2010-06-17 14:08 UTC, stevieschafer 		no flags Details
View All

Description stevieschafer 2010-06-17 14:08:32 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior-fd=18
component: gnome-panel
crash_function: wncklet_connect_while_alive
executable: /usr/libexec/wnck-applet
global_uuid: d072d5918b34f7ad13dfdb2af49a410eb5877226
kernel: 2.6.33.5-124.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
-----
1.
2. 
3.
Comment 1 stevieschafer 2010-06-17 14:08:35 UTC 
Created attachment 424829 [details]
File: backtrace
Comment 2 Jeff Raber 2010-06-21 18:02:39 UTC 
Thank you for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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