Bug 747072 - [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)
Summary: [abrt] gnome-applet-alarm-clock-0.3.2-1.fc14: alarm_settings_changed_time: Pr...
Keywords:
Status: CLOSED DUPLICATE of bug 696093
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applet-alarm-clock
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7f04829a0669e6892b60557750e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-18 17:55 UTC by dpw818
Modified: 2012-03-20 18:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 18:09:10 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (25.11 KB, text/plain)
2011-10-18 17:55 UTC, dpw818 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.