Bug 754350 - [abrt] gnome-panel-2.30.0-1.fc13: wncklet_connect_while_alive: Process /usr/libexec/wnck-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-panel-2.30.0-1.fc13: wncklet_connect_while_alive: Process /usr/l...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 13
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:177ab2fb540d43ecb5d888ee99b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-16 09:00 UTC by m.o.bugzilla
Modified: 2016-02-10 14:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-26 09:29:22 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (24.32 KB, text/plain)
2011-11-16 09:00 UTC, m.o.bugzilla 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description m.o.bugzilla 2011-11-16 09:00:38 UTC 
abrt version: 1.1.14
architecture: x86_64
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
kernel: 2.6.34.9-69.fc13.x86_64
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)
time: 1321433924
uid: 500

How to reproduce
-----
1.right mouse click un desktop selector
2.
3.
Comment 1 m.o.bugzilla 2011-11-16 09:00:43 UTC 
Created attachment 533930 [details]
File: backtrace
Comment 2 Jan Kurik 2015-12-22 11:30:01 UTC 
This bug is currently assigned to an unsupported release. If you think this bug is still valid and should remain open, please re-assign it to a supported release (F22, F23) or to rawhide.

Bugs which will be assigned to an unsupported release are going to be closed as EOL (End Of Life) on January 26th, 2016.
Note You need to log in before you can comment on or make changes to this bug.