ubuntu-sdk-bugs team mailing list archive

[Nekhelesh Ramananthan <krnekhelesh@xxxxxxxxx>]

This is confirmed to not be a bug in the UI Toolkit. hence marking it
invalid for that project alone.

** Changed in: ubuntu-clock-app
     Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Changed in: ubuntu-clock-app
       Status: Triaged => Fix Committed

** Changed in: ubuntu-ui-toolkit
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtorganizer5-eds in Ubuntu.
https://bugs.launchpad.net/bugs/1272333

Title:
  Saving an alarm does not work reliably

Status in Clock application for Ubuntu devices:
  Fix Committed
Status in Ubuntu UI Toolkit:
  Invalid
Status in “qtorganizer5-eds” package in Ubuntu:
  Fix Released

Bug description:
  I and Alan Pope have noticed that saving alarms on the Nexus 4 (or
  perhaps other devices) is not reliable. It so happens that when you
  save an alarm, it does not appear as saved unless you wait for 20
  minutes or more. Sometimes it only appears after you restart the
  phone.

  Is there any log that we can attach to this bug report to help
  reproduce it on your end?

  Steps to reproduce (on phone):
  1. Open clock app and navigate to the alarms tab
  2. Create an alarm and save it

  What should happen
  The newly saved alarm appears in the alarm tab

  What actually happens
  The newly saved alarm does not appear at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1272333/+subscriptions