when creating an alarm, app can reach a state where hour can't be set

[Charles Kerr]

See linked video.

This is consistently repeatable for me with these prerequisites: (1) I try to set the alarm immediately after the clock app is launched, and (2) I try to tap on the desired alarm hour instead of dragging the hour hand to it. Once those two prerequisites are done, I get the behavior in the video:

1. Dragging the hour hand updates the new alarm's minute property, leaving the hour unchanged. Even though the minute property tracks the user's finger movement, the hour hand itself doesn't move.

2. If you try a second time to drag the hour hand, it still won't move, nor will any of the alarm's properties change.

3. Clicking on the time in the middle of the clock seems to reset the state s.t. you can then drag the hour hand and set the hour properly.

4. Clicking on the time in the middle of the clock a second time correctly switches to the setting-the-minute-property mode. At this point the minute hand shown, and the minute property shown in the time in the middle of the clock, are out of sync with each other.

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:ubuntu-clock-app at revision 413, scheduled for release in ubuntu-clock-app, milestone 2.2

[Nekhelesh Ramananthan (nik90)]

I was able to reproduce this in the old clock app recently. Reopening bug. However it most likely won't be fixed since we have a new design for the new clock app.