Comment 13 for bug 977110

Interesting... From the logs it appears you are creating a new alarm (#4)
but there is no mention of the sound-repeat gconf key being set. On my
system, this key is set to true for all new alarms.

Can you try the following:
1. Create a new alarm, name it "Bug 977110"
2. Paste here the output of the command: gconftool-2 -R /apps/alarm-clock

Finally, is the issue reproducible from alarm-clock trunk?

Thanks!

On Sat, Apr 14, 2012 at 02:36, Chow Loong Jin <email address hidden> wrote:

> On 14/04/2012 07:10, Johannes H. Jensen wrote:
> > On Sat, Apr 14, 2012 at 00:54, Chow Loong Jin <email address hidden>
> wrote:
> >>
> >> Here you go. The former command does not work as G_LOG_DOMAIN was not
> >> defined
> >> during the build, but the latter does.
> >
> >
> > Thank you. Is that log output captured while you trigger the sound_repeat
> > bug?
> >
>
> Yep, specifically this snippet:
>
> ----
> ** (alarm-clock-applet:10081): DEBUG: AlarmSettingsDialog: preview_start...
> ** (alarm-clock-applet:10081): DEBUG: AlarmSettingsDialog: Freeing media
> player
> 0x1d40d20
> ** (alarm-clock-applet:10081): DEBUG: AlarmSettingsDialog: preview_start...
> ** (alarm-clock-applet:10081): DEBUG: AlarmSettingsDialog: Freeing media
> player
> 0x20a50a0
> ** (alarm-clock-applet:10081): DEBUG: AlarmSettingsDialog: preview_start...
> ** (alarm-clock-applet:10081): DEBUG: AlarmSettingsDialog: Freeing media
> player
> 0x1b31a40
> ----
>
> In all three cases, the sound played once, while the "Play" button remained
> depressed until manually released by the second click.
>
> --
> Kind regards,
> Loong Jin
>
> --
> You received this bug notification because you are subscribed to Alarm
> Clock.
> https://bugs.launchpad.net/bugs/977110
>
> Title:
> sound_repeat option not working
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/alarm-clock/+bug/977110/+subscriptions
>