Bug 616229 - [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...
Status: CLOSED DUPLICATE of bug 552423
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:552a72964bfae2de82eda3465ff...
Keywords: Triaged
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-19 21:10 UTC by Shaiaqua
Modified: 2010-07-28 03:23 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2010-07-28 03:23:42 UTC

Attachments (Terms of Use)
File: backtrace (15.73 KB, text/plain)
2010-07-19 21:10 UTC, Shaiaqua
no flags Details

Description Shaiaqua 2010-07-19 21:10:51 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
comment: The workspace switcher enters this state sporadically; I don't know what causes it, but it reliably crashes along with the panel and window list when the above steps are followed. 
component: gnome-panel
crash_function: wncklet_connect_while_alive
executable: /usr/libexec/wnck-applet
global_uuid: 552a72964bfae2de82eda3465fff3f23d972ccc3
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
When the workspace switcher does not respond to the mouse wheel (which should change the workspace) but does to clicks:
1.Right click on workspace switcher
2.Select preferences

Comment 1 Shaiaqua 2010-07-19 21:10:53 UTC
Created attachment 433009 [details]
File: backtrace

Comment 2 Jeff Raber 2010-07-28 03:23:42 UTC
Fedora Bugzappers volunteer triage team

Fedora Bugzappers volunteer triage team

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