Bug 701367 - [abrt] gnome-panel-2.32.0.2-2.fc14: g_type_check_instance_cast: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: g_type_check_instance_cast: Process /usr/...
Keywords:
Status: CLOSED DUPLICATE of bug 684406
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e188fb7b71fa5bad7b7df2505eb...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-02 17:32 UTC by rec7788
Modified: 2012-03-20 15:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 15:58:44 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (28.79 KB, text/plain)
2011-05-02 17:32 UTC, rec7788 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description rec7788 2011-05-02 17:32:55 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 29483 bytes
cmdline: /usr/libexec/clock-applet
component: gnome-panel
Attached file: coredump, 22298624 bytes
crash_function: g_type_check_instance_cast
executable: /usr/libexec/clock-applet
kernel: 2.6.35.12-90.fc14.x86_64
package: gnome-panel-2.32.0.2-2.fc14
rating: 4
reason: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1304108542
uid: 500

How to reproduce
-----
1.Open a new clock applet on desktop 0.1.
2.
3.
Comment 1 rec7788 2011-05-02 17:32:57 UTC 
Created attachment 496321 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 15:58:44 UTC 
Backtrace analysis found this bug to be similar to bug #684406, closing as duplicate.

Bugs which were found to be similar to this bug: bug #646867, bug #684406

This comment is automatically generated.

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