Steps I used to test this: 1. ssh'ed into the phablet
2. built lp:~charlesk/indicator-datetime/log-instances-to-terminal, which is stock indicator-datetime plus this console message: http://bazaar.launchpad.net/~charlesk/indicator-datetime/log-instances- to-terminal/revision/337 3. "$ stop indicator-datetime" to kill the system copy of indicator- datetime 4. "$ log-instances-to-terminal/build/src/indicator-datetime-service" to start up the test build to run in its place What happens: The times returned by e_cal_client_generate_instances() get dumped to the terminal and match the alarms' old values, instead of the new ones, until I kill evolution-calendar-factory and restart. -- You received this bug notification because you are a member of Unity API bugs, which is subscribed to Indicator Date and Time. https://bugs.launchpad.net/bugs/1283859 Title: Updated recurring alarm values are not reflected in the indicator until phone reboot Status in The Date and Time Indicator: New Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UI Toolkit: New Status in “qtorganizer5-eds” package in Ubuntu: Confirmed Bug description: Mako 205 Steps to reproduce: 1. Create a recurring alarm and save it 2. Select the saved alarm to go to edit mode 3. Change the time, day of the alarm or status of the alarm. 4. Hit save What happens: The alarm is correctly updated in the clock app. The indicator however still shows the old alarm time What should happen: The alarm is correctly updated *both* in the clock app and the indicator. If you however reboot the phone, the indicator then shows the updated recurring alarm time. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1283859/+subscriptions -- Mailing list: https://launchpad.net/~unity-api-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~unity-api-bugs More help : https://help.launchpad.net/ListHelp
