Opened bug #1583639 for a real API ** Changed in: canonical-developer-experience Importance: Undecided => Medium
** Changed in: canonical-developer-experience Assignee: (unassigned) => Alejandro J. Cura (alecu) ** No longer affects: canonical-developer-experience -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1480200 Title: indicator-datetime starting ringing almost immediately if timer is set in current minute Status in Canonical System Image: Confirmed Status in Timer: Confirmed Status in Ubuntu Clock App: Incomplete Status in indicator-datetime package in Ubuntu: Confirmed Bug description: indicator-datetime doesn't check seconds for alarms. Reproduce scenario 1. Let's say we have time: 22:00:20 2. If I set Alarm for 22:00:10, then alarm rings immedietely, which is ok. 3. Unfortunately when I set Alarm to 22:00:50, it will also start ringing immedietely Currently: 4. Alarm is ringing immediately (22:00:20) Expected: 4. Alarm is ringing after 30 seconds 22:00:50 It is an blocker for Timer implementation in Clock app: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1427566 Old description: Steps to reproduce: 1. Install Timer: https://uappexplorer.com/app/timer.mivoligo 2. Set timer to 15 seconds in current minute 3. Start timer Currently: 4. Alarm is ringing immediately if it is set in current minute Expected: 4. Alarm is ringing after 15 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp