alarms sceduled within the current minute trigger immediately
Bug #1447332 reported by
Michael Zanetti
This bug report is a duplicate of:
Bug #1480200: indicator-datetime starting ringing almost immediately if timer is set in current minute.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| indicator-datetime (Ubuntu) |
Triaged
|
Medium
|
Charles Kerr | ||
Bug Description
Use case: a countdown timer.
As an app might be suspended by the time the countdown hits 0, currently the alarm api is the only way to create such apps. However, for that use case there would be a requirement for second-precision at least.
Currently, when a countdown is set to some few seconds, staying within the current minute, the alarm will trigger immediately when it is synced to the datetime-indicator, instead of waiting for the time to trigger.
If the alarm is longer, passing the next minute, it seems to actually trigger it on the right time.
Here's an countdown app for testing that sets a countdown to 20 secs from now: lp:~mzanetti/+junk/stopwatch-countdown
| description: | updated |
| summary: |
- alarms have minute-precision only, should be seconds + alarms sceduled within the current minute trigger immediately |
| description: | updated |
| Changed in indicator-datetime (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| assignee: | nobody → Charles Kerr (charlesk) |
To post a comment you must log in.
