Bug 586673 - [abrt] crash in gnome-panel-2.28.0-16.fc12: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-panel-2.28.0-16.fc12: Process /usr/libexec/clock-applet...
Keywords:
Status: CLOSED DUPLICATE of bug 573219
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:79ec240835720e638c85125e804...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-28 06:13 UTC by Alex Bartl
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:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (20.88 KB, text/plain)
2010-04-28 06:13 UTC, Alex Bartl
no flags Details

Description Alex Bartl 2010-04-28 06:13:45 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=30
component: gnome-panel
executable: /usr/libexec/clock-applet
global_uuid: 79ec240835720e638c85125e804339679fa4ae1b
kernel: 2.6.32.11-99.fc12.i686
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. From default setting deleted the city boston, added a differnt city and tried to add another one right away
2.
3.

Comment 1 Alex Bartl 2010-04-28 06:13:48 UTC
Created attachment 409682 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:07:51 UTC

*** This bug has been marked as a duplicate of bug 573219 ***

Comment 3 Karel Klíč 2010-05-25 09:07:51 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.