alarm-clock-applet crashed with SIGSEGV in media_player_start()

[Rosalvo]

Binary package hint: alarm-clock-applet

The alarm-clock-applet don't works nor works with music track. Would it incompatible with Maverick?

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: alarm-clock-applet 0.3.1-1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Sep 24 08:13:20 2010
ExecutablePath: /usr/bin/alarm-clock-applet
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100830)
ProcCmdline: /usr/bin/alarm-clock-applet
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8050854 <media_player_start+20>: mov (%ebx),%eax
 PC (0x08050854) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: alarm-clock-applet
StacktraceTop:
 media_player_start ()
 g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: alarm-clock-applet crashed with SIGSEGV in media_player_start()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (process:1472): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 media_player_start (player=0x0) at player.c:212
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 645081, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.