Bug 619483 - [abrt] crash in gnome-panel-2.30.0-4.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-4.fc13: do_idle_run_queue: Process /usr/li...
Keywords:
Status: CLOSED DUPLICATE of bug 590834
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:963e3463a9f49e134c631ae09bd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-29 16:21 UTC by Omar Benabdouallah
Modified: 2010-11-08 09:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 09:31:29 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (20.47 KB, text/plain)
2010-07-29 16:21 UTC, Omar Benabdouallah 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Omar Benabdouallah 2010-07-29 16:21:25 UTC 
abrt 1.1.1 detected a crash.

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

How to reproduce
-----
1. J'ai ajout une nouvelle ville dans l'applet puis aprs validation l'erreur est leve.
2.
3.
Comment 1 Omar Benabdouallah 2010-07-29 16:21:28 UTC 
Created attachment 435341 [details]
File: backtrace
Comment 2 Jeff Raber 2010-11-08 09:31:29 UTC 

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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