Bug 596336 - [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:8e95ac85242381ee3a7ea7efefe...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-26 15:52 UTC by Garland Binns
Modified: 2010-06-03 15:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-03 15:43:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (23.98 KB, text/plain)
2010-05-26 15:52 UTC, Garland Binns
no flags Details

Description Garland Binns 2010-05-26 15:52:53 UTC
abrt 1.1.0 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: This typically only happens when my laptop is in it's docking station and I am using an additional monitor.
component: gnome-panel
crash_function: wncklet_connect_while_alive
executable: /usr/libexec/wnck-applet
global_uuid: 8e95ac85242381ee3a7ea7efefeef143f3687fca
kernel: 2.6.33.4-95.fc13.i686.PAE
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
-----
All I need to do to create this error is right-click and select the Workspace Switcher preferences.

Comment 1 Garland Binns 2010-05-26 15:52:54 UTC
Created attachment 416898 [details]
File: backtrace

Comment 2 Jeff Raber 2010-06-03 15:43:20 UTC
Sorry for the noise.  NEEDINFO was set accidently.  Closing as dup of 552423.

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