Hey freemangordon,

your guinea pig maybe has something new?

But it could also be caused again by hildon-home (you remember? ). I cannot remember 100% if I had that behaviour before using your lib, but I think so that it happened to me before ...

I had an alarm ringing this morning (yeah, ringing with sound), popup came up asking to snooze or stop. But as I wanted to snooze: no chance. No reaction on stop either. Even pressing beside that pop up did not do anything. Nor pushing the power button helped.
So I let it ring out and relied on my N9 to wake me up

After waking up I could push snooze and popup came up again after 5 minutes. Then I pushed stop and it vanished.

Then I checked my logs and they showed that at waking up the hildon-home was not frozen (at least not with "read(xx, <unfinished>". But after I was able to push stop, the h-h was frozen. And it got unlocked by my script some time later.

Any idea why the pop up did not react?

--edit
rechecked my logs
and after rethinking that shows that most probable the h-h was not frozen at ring time (08:15), but got instantly at the pop up came up. I think, h-h got waked up to show the alarm ui pop up, hereby trying to update the widgets (event: on desktop change) and BOOM: hanging. So no reaction anymore possible to the popup. And that also explains why the snoozes did not ring.
And also
So looks like a h-h problem again, hmm?

But what I do not get (yet) is why did the pop up not respond first (but rang), but on second snooze pop (not ringing)?
I checked manually the "hanging" status at 08:20.and that showed So it should have still been unresponsive, or?

--another edit
Oops, sorry.
Think this post belongs to this thread: [ANNOUNCE] Alarm-UI replacement.
So I copied this post and pasted it there. Let us continue in that thread.