Bug 592802

Summary: [abrt] crash in gnome-applet-alarm-clock-0.2.6-1.fc12: media_player_start: Process /usr/libexec/alarm-clock-applet was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Akendo <4k3nd0>
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:85bb9189d3ae758eaa1ccac9dca8a0cf082623a2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-17 12:12:08 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 Akendo 2010-05-17 02:22:46 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=34
component: gnome-applet-alarm-clock
crash_function: media_player_start
executable: /usr/libexec/alarm-clock-applet
global_uuid: 85bb9189d3ae758eaa1ccac9dca8a0cf082623a2
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)

How to reproduce
-----
1. Simply using the Applet with a sound
2.
3.
Comment 1 Akendo 2010-05-17 02:22:49 UTC 
Created attachment 414440 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-05-17 12:12:08 UTC 
This is already fixed in gnome-applet-alarm-clock-0.3.0-1.fc12. Please install the package from updates-testing and provide some feedback at
http://admin.fedoraproject.org/updates/gnome-applet-alarm-clock-0.3.0-1.fc12

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