Bug 601459

Summary: [abrt] crash in gnome-applet-alarm-clock-0.3.0-1.fc12: raise: Process /usr/bin/alarm-clock-applet was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Misha Shnurapet <zayzayats>
Component: gnome-applet-alarm-clockAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:1d00b7ba4ca0e6db2a51d0c5e36f625d2b891813
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-12 09:16:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Misha Shnurapet 2010-06-08 02:44:06 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: alarm-clock-applet
component: gnome-applet-alarm-clock
crash_function: raise
executable: /usr/bin/alarm-clock-applet
global_uuid: 1d00b7ba4ca0e6db2a51d0c5e36f625d2b891813
kernel: 2.6.32.12-115.fc12.x86_64
package: gnome-applet-alarm-clock-0.3.0-1.fc12
rating: 4
reason: Process /usr/bin/alarm-clock-applet was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 Misha Shnurapet 2010-06-08 02:44:10 UTC 
Created attachment 421995 [details]
File: backtrace
Comment 2 Misha Shnurapet 2010-06-08 07:43:08 UTC 
Package: gnome-applet-alarm-clock-0.3.0-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


Comment
-----
Turned the alarm off by clicking on the notification icon and clicked immediately once more to bring up the settings dialog. It crashed instead.
Comment 3 Christoph Wickert 2010-06-12 09:16:31 UTC 
I'm pretty confident that this is a duplicate of bug 597562, but the backtrace lacks the necessary debug info, so I cannot be 100% sure.

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