Bug 592558 - [abrt] crash in gnome-panel-2.28.0-16.fc12: do_idle_run_queue: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-panel-2.28.0-16.fc12: do_idle_run_queue: Process /usr/l...
Keywords:
Status: CLOSED DUPLICATE of bug 572829
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:12489053ea7864ed059ffa45145...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-15 11:44 UTC by Nivag
Modified: 2010-05-25 08:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 08:49:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (24.06 KB, text/plain)
2010-05-15 11:44 UTC, Nivag 		no flags Details
View All

Description Nivag 2010-05-15 11:44:11 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=47
comment: Don't know
component: gnome-panel
crash_function: do_idle_run_queue
executable: /usr/libexec/clock-applet
global_uuid: 12489053ea7864ed059ffa451459c360424c7fc5
kernel: 2.6.32.11-99.fc12.x86_64
package: gnome-panel-2.28.0-16.fc12
rating: 4
reason: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.deleted boston
2.added  5 or 6 locations
3.crash
Comment 1 Nivag 2010-05-15 11:44:14 UTC 
Created attachment 414238 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:49:57 UTC 

*** This bug has been marked as a duplicate of bug 572829 ***
Comment 3 Karel Klíč 2010-05-25 08:49:57 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #572829.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.