indicator-datetime starting ringing almost immediately if timer is set in current minute
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Confirmed
|
Medium
|
Alejandro J. Cura | ||
Timer |
Confirmed
|
Undecided
|
Unassigned | ||
Ubuntu Clock App |
Incomplete
|
Undecided
|
Unassigned | ||
indicator-datetime (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
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:/
Old description:
Steps to reproduce:
1. Install Timer: https:/
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
description: | updated |
no longer affects: | indicator-datetime |
Changed in ubuntu-clock-app: | |
status: | New → Incomplete |
no longer affects: | ubuntu-ui-toolkit |
summary: |
- indicator-datetime doesn't check seconds for alarms + indicator-datetime starting ringing almost immedietly if timer is set + for less than 60 seconds |
Changed in timer: | |
status: | New → Confirmed |
no longer affects: | ubuntu-clock-app (Ubuntu) |
no longer affects: | ubuntu-ui-toolkit (Ubuntu) |
description: | updated |
summary: |
- indicator-datetime starting ringing almost immedietly if timer is set + indicator-datetime starting ringing almost immediately if timer is set for less than 60 seconds |
summary: |
indicator-datetime starting ringing almost immediately if timer is set - for less than 60 seconds + in current minute |
description: | updated |
description: | updated |
description: | updated |
Changed in canonical-developer-experience: | |
status: | New → Confirmed |
Status changed to 'Confirmed' because the bug affects multiple users.