Bug 589364

Summary: [abrt] crash in gnome-applet-alarm-clock-0.2.6-1.fc12: IA__g_type_check_instance_cast: Process /usr/libexec/alarm-clock-applet was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Joe Julian <joe>
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:92868d31ae4f431ca8b9bdaf64f25194fda0f04e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-06 06:20:41 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 Joe Julian 2010-05-05 23:21:35 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/alarm-clock-applet --oaf-activate-iid=OAFIID:AlarmClock_Factory --oaf-ior-fd=18
comment: I had unchecked and rechecked an alarm.
component: gnome-applet-alarm-clock
crash_function: IA__g_type_check_instance_cast
executable: /usr/libexec/alarm-clock-applet
global_uuid: 92868d31ae4f431ca8b9bdaf64f25194fda0f04e
kernel: 2.6.32.11-99.fc12.x86_64
package: gnome-applet-alarm-clock-0.2.6-1.fc12
rating: 4
reason: Process /usr/libexec/alarm-clock-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Joe Julian 2010-05-05 23:21:37 UTC
Created attachment 411762 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-05-06 06:20:41 UTC
Please try 0.3.0 from updates-tesing, I'm pretty sure it's fixed there.

Please provide feedback at
https://admin.fedoraproject.org/updates/gnome-applet-alarm-clock-0.3.0-1.f12

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