Bug 747072

Summary: [abrt] gnome-applet-alarm-clock-0.3.2-1.fc14: alarm_settings_changed_time: Process /usr/bin/alarm-clock-applet was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: dpw818
Component: gnome-applet-alarm-clockAssignee: Christoph Wickert <cwickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: cwickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:7f04829a0669e6892b60557750e98d8c0f0d3f6a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 18:09:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description dpw818 2011-10-18 17:55:17 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 25708 bytes
cmdline: alarm-clock-applet --hidden
component: gnome-applet-alarm-clock
Attached file: coredump, 54067200 bytes
crash_function: alarm_settings_changed_time
executable: /usr/bin/alarm-clock-applet
kernel: 2.6.35.14-96.fc14.i686.PAE
package: gnome-applet-alarm-clock-0.3.2-1.fc14
rating: 4
reason: Process /usr/bin/alarm-clock-applet was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: Snoozed, then re-set a new time, and apparently it crashed.
time: 1318949084
uid: 500
Comment 1 dpw818 2011-10-18 17:55:20 UTC 
Created attachment 528857 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 18:09:10 UTC 
Backtrace analysis found this bug to be similar to bug #696093, closing as duplicate. This bug seems to belong to component gtk2.

This comment is automatically generated.

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