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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283859 Title: Updated recurring alarm values are not reflected in the indicator until phone reboot To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1283859/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
