touch-packages team mailing list archive

[Ted Gould <ted@xxxxxxxx>]

For a data point, I've seen this a couple times before the timerfd stuff
landed. So I'm pretty sure that isn't the culprit.

I've not been able to recreate it reliably. But with U8 in Vivid, I've
been rebooting a lot :-)

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

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

** Summary changed:

- Sometimes indicator-datetime is not available in the UI after a reboot (vivid/mako 110)
+ Sometimes indicator-datetime is not available in the UI after a reboot (vivid/mako)

-- 
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/1425297

Title:
  Sometimes indicator-datetime is not available in the UI after a reboot
  (vivid/mako)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 04:34:45
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  See the attached picture.

  The only log entry I have for it:
  Indicator-Datetime-Message: static gboolean unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond(gint, GIOCondition, gpointer) triggered at 2015-02-24 20:24:48.605449 by GIOCondition 1, read -1 bytes, found 0 interrupts

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