touch-packages team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

Public bug reported:

Not the same as the bug #1328646, where the clock fell totally out-of-
sync.

This variation is milder, it can take up to a minute for the clock to
update after resume from suspend.

We could listen to powerd's Wakeup signal and also 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>

Reported by ogra and dednick in #ubuntu-touch.

** Affects: indicator-datetime (Ubuntu)
     Importance: High
     Assignee: Charles Kerr (charlesk)
         Status: Triaged

** Changed in: indicator-datetime (Ubuntu)
     Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-datetime (Ubuntu)
       Status: New => Triaged

-- 
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 screen turned on

Status in “indicator-datetime” package in Ubuntu:
  Triaged

Bug description:
  Not the same as the bug #1328646, where the clock fell totally out-of-
  sync.

  This variation is milder, it can take up to a minute for the clock to
  update after resume from suspend.

  We could listen to powerd's Wakeup signal and also 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>

  Reported by ogra and dednick in #ubuntu-touch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1359802/+subscriptions