This bug was fixed in the package qtorganizer5-eds - 0.1.1+14.04.20140131-0ubuntu1
--------------- qtorganizer5-eds (0.1.1+14.04.20140131-0ubuntu1) trusty; urgency=low [ Renato Araujo Oliveira Filho ] * Make sure that allDay property get saved correct. (LP: #1265953) * Fixed todo event parse. (LP: #1272333) -- Ubuntu daily release <[email protected]> Fri, 31 Jan 2014 11:37:04 +0000 ** Changed in: qtorganizer5-eds (Ubuntu) Status: Confirmed => Fix Released -- 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: Triaged Status in Ubuntu UI Toolkit: New 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 -- Mailing list: https://launchpad.net/~ubuntu-sdk-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs More help : https://help.launchpad.net/ListHelp
