Bug 600709 - [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:061a36b75bfc061c86ac81bb8cd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-05 17:52 UTC by JWincn
Modified: 2010-06-06 02:01 UTC (History)
2 users (show)

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


Attachments (Terms of Use)
File: backtrace (17.43 KB, text/plain)
2010-06-05 17:52 UTC, JWincn
no flags Details

Description JWincn 2010-06-05 17:52:04 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: The workspace switcher applet routinely starts without displaying previously assigned workspace names and numbers.  My first work-around is to log-out and log-in.  My second work-around is to open "preferences" for the applet.  That second option triggers a restart of the applet, the restart triggered this bug report.
component: gnome-panel
crash_function: wncklet_connect_while_alive
executable: /usr/libexec/wnck-applet
global_uuid: 061a36b75bfc061c86ac81bb8cdffe9cb8d67477
kernel: 2.6.32.12-115.fc12.i686.PAE
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)

How to reproduce
-----
1. log-in
2.
3.

Comment 1 JWincn 2010-06-05 17:52:06 UTC
Created attachment 421464 [details]
File: backtrace

Comment 2 Jeff Raber 2010-06-06 02:01:44 UTC

*** 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.