@lukasz, yeah this would also be affecting vivid. However at the moment
the alarms feature in vivid is broken badly due to SDK Alarms API
(alarms backend rewritten for performance and other benefits). Thereby
it is difficult to identify if fixes like the above work or not. I would
recommend waiting for the SDK Alarms API to settle down a bit in vivid
before pushign this fix to vivid.
** Changed in: ubuntu-clock-app
Status: Confirmed => Fix Released
--
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/1411171
Title:
Repeating alarms appear disabled in clock app after it went off once
Status in the base for Ubuntu mobile products:
Confirmed
Status in Clock application for Ubuntu devices:
Fix Released
Status in indicator-datetime package in Ubuntu:
In Progress
Status in indicator-datetime package in Ubuntu RTM:
Fix Released
Bug description:
krillin #198
Repeating alarm is disabled after the first time it goes off.
Test Case:
1. Setup a repeating alarm (everyday from Monday to Friday for example) and
enable it
2. Close the clock app
3. Wait until it goes off
4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next
occurrence)
5. Resume the device
6. Launch the clock app
7. Go the alarms and verify the status of the alarm
Actual Result:
The alarm is disabled but it shows in the indicator.
The next and next-next occurrences of the alarm are scheduled correctly.
Expected Result
Alarm is still enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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
