Bug 591462 - [abrt] crash in gnome-panel-2.30.0-1.fc13: do_idle_run_queue: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-panel-2.30.0-1.fc13: do_idle_run_queue: Process /usr/li...
Keywords:
Status: CLOSED DUPLICATE of bug 572829
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e17e7d8a20722d781b32acb69ba...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-12 10:11 UTC by Diogo Lima
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:52 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (19.24 KB, text/plain)
2010-05-12 10:11 UTC, Diogo Lima 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Diogo Lima 2010-05-12 10:11:41 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=34
component: gnome-panel
crash_function: do_idle_run_queue
executable: /usr/libexec/clock-applet
global_uuid: e17e7d8a20722d781b32acb69ba22111bcd1bb2e
kernel: 2.6.33.3-85.fc13.x86_64
package: gnome-panel-2.30.0-1.fc13
rating: 4
reason: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

comment
-----
It crashed when I tried to add Rio de Janeiro, zone on the clock watch.

After restarting the applet it no longer happens.

How to reproduce
-----
1. Go to the clock options
2. Add a New zone (Rio de Janeiro/Sao_Paulo)
3.
Comment 1 Diogo Lima 2010-05-12 10:11:43 UTC 
Created attachment 413384 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:49:52 UTC 

*** This bug has been marked as a duplicate of bug 572829 ***
Comment 3 Karel Klíč 2010-05-25 08:49:52 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.