Public bug reported:
In Vivid, the clock app cannot edit alarm correctly since the alarm
times chosen is not taken into account due to timezone management by the
Ubuntu SDK Alarms Backend.
Steps to reproduce:
1. In the latest vivid images, open the clock app
2. Create a new alarm to ring in the next few minutes and save it.
3. Edit the alarm and change the time.
4. save the alarm
What happens:
The alarm is not updated with the new alarm time chosen in step 3
What should happen
The newly changed alarm time should be used.
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
In Vivid, the clock app cannot edit alarm correctly since the alarm
times chosen is not taken into account due to timezone management by the
Ubuntu SDK Alarms Backend.
+
+ Steps to reproduce:
+ 1. In the latest vivid images, open the clock app
+ 2. Create a new alarm to ring in the next few minutes and save it.
+ 3. Edit the alarm and change the time.
+ 4. save the alarm
+
+ What happens:
+ The alarm is not updated with the new alarm time chosen in step 3
+
+ What should happen
+ The newly changed alarm time should be used.
** Summary changed:
- [Vivid][Regression] Alarms times is incorrectly saved when editing an alarm
+ [Vivid][Regression] Alarms times are incorrectly saved when editing an alarm
--
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1401883
Title:
[Vivid][Regression] Alarms times are incorrectly saved when editing an
alarm
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
In Vivid, the clock app cannot edit alarm correctly since the alarm
times chosen is not taken into account due to timezone management by
the Ubuntu SDK Alarms Backend.
Steps to reproduce:
1. In the latest vivid images, open the clock app
2. Create a new alarm to ring in the next few minutes and save it.
3. Edit the alarm and change the time.
4. save the alarm
What happens:
The alarm is not updated with the new alarm time chosen in step 3
What should happen
The newly changed alarm time should be used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1401883/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help : https://help.launchpad.net/ListHelp
