Activity log for bug #885059

Date Who What changed Old value New value Message
2011-11-02 04:00:00 Chops II bug added bug
2011-11-03 16:58:22 Johannes H. Jensen alarm-clock: importance Undecided Low
2011-11-03 16:58:22 Johannes H. Jensen alarm-clock: status New Confirmed
2012-03-15 18:39:38 Johannes H. Jensen alarm-clock: milestone 0.3.3
2012-03-18 16:32:27 Johannes H. Jensen alarm-clock: status Confirmed Fix Committed
2012-03-18 16:32:27 Johannes H. Jensen alarm-clock: assignee Johannes H. Jensen (joh)
2012-06-03 19:52:09 Johannes H. Jensen alarm-clock: status Fix Committed Fix Released
2012-06-04 04:25:22 Launchpad Janitor branch linked lp:debian/alarm-clock-applet
2012-06-04 12:16:07 Chow Loong Jin bug task added alarm-clock-applet (Ubuntu)
2012-06-04 12:16:46 Chow Loong Jin alarm-clock-applet (Ubuntu): status New Fix Released
2012-06-04 12:18:47 Chow Loong Jin nominated for series Ubuntu Precise
2012-06-04 12:18:47 Chow Loong Jin bug task added alarm-clock-applet (Ubuntu Precise)
2012-06-04 12:18:47 Chow Loong Jin nominated for series Ubuntu Quantal
2012-06-04 12:18:47 Chow Loong Jin bug task added alarm-clock-applet (Ubuntu Quantal)
2012-06-04 20:39:18 Chow Loong Jin bug added subscriber Ubuntu Stable Release Updates Team
2012-06-04 20:39:18 Chow Loong Jin alarm-clock-applet (Ubuntu Precise): status New Confirmed
2012-06-13 22:25:54 Clint Byrum description Start a timer, then edit it while its still ticking and set to alarm. For a more reasonable use case that shows the bug, create an alarm, start it, notice the correct count down. While still running, edit, set to timer, then back to alarm, notice incorrect countdown (timer like one). [test case] Start a timer, then edit it while its still ticking and set to alarm. For a more reasonable use case that shows the bug, create an alarm, start it, notice the correct count down. While still running, edit, set to timer, then back to alarm, notice incorrect countdown (timer like one).
2012-06-16 11:05:19 Chow Loong Jin description [test case] Start a timer, then edit it while its still ticking and set to alarm. For a more reasonable use case that shows the bug, create an alarm, start it, notice the correct count down. While still running, edit, set to timer, then back to alarm, notice incorrect countdown (timer like one). [Test Case] 1. Click on the alarm-clock-applet indicator and click "Show alarms" 2. Create a new alarm. 3. Close the new alarm dialog and start the alarm. 4. Observe the countdown -- it should be accurate, counting down towards the time specified in the alarm properties dialog. 5. Double click the alarm to edit it. 6. Without changing any other setting, change the alarm into a timer by clicking the "Timer" button next to the "Alarm" button on top. 7. Close the dialog 8. Check if the countdown now reflects that of a timer (counting down to 0, based on the amount of time specified in the timer properties dialog), or if it continues counting as per the observation in step 4. If this bug is fixed, it should now follow the countdown of a timer, rather than an alarm. [Regression potential] Unlikely.
2021-10-14 05:36:18 Steve Langasek alarm-clock-applet (Ubuntu Precise): status Confirmed Won't Fix