** Changed in: ubuntu-clock-app
Milestone: alarm-blockers => rtm
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/1321294
Title:
Editing a single type alarm after the alarm has gone of results in the
alarm not ringing
Status in The Date and Time Indicator:
New
Status in Clock application for Ubuntu devices:
Triaged
Status in Ubuntu UI Toolkit:
New
Bug description:
This is a bug which could be due to the SDK, clock app, EDS or
indicator-datetime. As a result I would like to do investigations in
these projects and determine the exact cause of this.
Steps to reproduce this bug:
1. Create a single type alarm to ring in the next 3-4 minutes
2. Wait for that alarm to ring.
3. After dismissing the alarm, edit the alarm and set it to ring in the next
3-4 minutes.
What happens:
The alarm does not ring the second time. It is shown as enabled in the clock
app, but it still doesn't ring. The updated alarm can also be seen in the
indicator-datetime.
What should happen:
well if the one time alarm is intended to ring only once, then the alarm
status should be shown correctly. If possible, the alarm should be deleted in
that case. If not, then after editing, it should also ring the second time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1321294/+subscriptions
--
Mailing list: https://launchpad.net/~unity-api-bugs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~unity-api-bugs
More help : https://help.launchpad.net/ListHelp
