Bug 583950 - [abrt] crash in gnome-panel-2.30.0-1.fc13: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-panel-2.30.0-1.fc13: Process /usr/libexec/clock-applet ...
Keywords:
Status: CLOSED DUPLICATE of bug 573219
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:c266f32659b460a167b5e644eca...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-20 10:45 UTC by t.jastrzebowski
Modified: 2010-05-25 09:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:07:47 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (17.98 KB, text/plain)
2010-04-20 10:45 UTC, t.jastrzebowski 		no flags Details
View All

Description t.jastrzebowski 2010-04-20 10:45:48 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=34
component: gnome-panel
executable: /usr/libexec/clock-applet
global_uuid: c266f32659b460a167b5e644eca3d1323770aad6
kernel: 2.6.33.2-41.fc13.i686.PAE
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)

How to reproduce
-----
1. added new time zone in the system's clock
2. tried to change default time zone
Comment 1 t.jastrzebowski 2010-04-20 10:45:50 UTC 
Created attachment 407786 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:07:47 UTC 

*** This bug has been marked as a duplicate of bug 573219 ***
Comment 3 Karel Klíč 2010-05-25 09:07:47 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 #573219.

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