This might be caused either by the same regression as in bug #1401883,
or because the app does not handle the switch state after the alarm
updates.
** Also affects: ubuntu-clock-app (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1425184
Title:
Alarm cannot be disabled
Status in ubuntu-clock-app package in Ubuntu:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
Test case.
- Create an alarm 5 minutes in the future.
- In the Alarm page, tap to the switcher to disable the alarm.
Expected result.
- Switcher goes to disabled position and alarm is disabled.
Actual result.
- Switcher remains in enabled position.
com.ubuntu.clock 3.3.192
current build number: 121
device name: krillin
channel: ubuntu-touch/devel-proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1425184/+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
