Not really sure how the suspend works, but maybe installing signal handler for SIG_CONT maybe to force a refresh would work?
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1359802 Title: header's timestamp can take a minute to update after resume from suspend Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: Not the same as the bug #1328646, where the clock fell completely out- of-sync and never came back. This bug has a milder but similar symptom, the clock is set to update once per minute, so after resume from suspend it will still show the wrong time until that periodic update timer triggers. In addition to the periodic update, indicator-datetime should listen to powerd's Wakeup signal, or better yet, to com.canonical.Unity.Screen's DisplayPowerStateChange signal <http://bazaar.launchpad.net/~unity-system-compositor-team/unity- system-compositor/trunk/view/head:/src/dbus_screen.cpp#L100> to ensure that it makes the timestamp up-to-date whenever the screen is turned on. Reported by ogra and dednick in #ubuntu-touch. *edit:* also discussed by kgunn72 and aacid @ https://code.launchpad.net/~nick- dedekind/unity8/lp1328646/+merge/231335 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1359802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
