alarms and event notifications causes time to freeze

[Michael Zanetti]

On latest vivid, snoozing an alarm causes the time in the indicator to freeze. Here's a screenshot of the phone after I snoozed an alarm today morning at 9am.

[Oliver Grawert (ogra)]

i see the same with calendar notifications (which only fire off once without "snoozing" ability) ... my clock was stuck at 17:30 (time of my last meeting and calendar notification) the whole evening yesterday which i only noticed around midnight and could only fix with a reboot ... the greeter clock seems affected as well.

[Charles Kerr (charlesk)]

I'm seeing this too in vivid r146 mako...

[Pat McGowan (pat-mcgowan)]

also saw after dismissing an alarm, so it seems all cases cause the time in the indicator to freeze

[Charles Kerr (charlesk)]

This is likely the pulse issue that pat, ogra, and I discussed in #phablet.

gdb trace of indicator-datetime-service when pressing the snooze button:

> Thread 1 (Thread 0xb470d000 (LWP 6431)):
> #0 0xb6e3ad24 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
> #1 0xb6e3677c in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
> #2 0xb4033516 in pa_threaded_mainloop_wait () from /usr/lib/arm-linux-gnueabihf/libpulse.so.0
> #3 0xb405738a in ?? () from /usr/lib/arm-linux-gnueabihf/gstreamer-1.0/libgstpulse.so

Which is being reached from a datetime-service call to gst_element_set_state (m_play, GST_STATE_NULL) to stop the alarm sound when the notification is closed.

[Charles Kerr (charlesk)]

This is likely the same root cause as bug #1435867, and is being triaged by rsalveti