[Bug 1567940] Re: time displayed wrongly on production phone

** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567940 Title: time displayed wrongly on production phone

[Bug 1567940] Re: time displayed wrongly on production phone

This bug was fixed in the package indicator-datetime - 15.10+16.04.20160516.2-0ubuntu2 --- indicator-datetime (15.10+16.04.20160516.2-0ubuntu2) yakkety; urgency=medium * No-change rebuild for libical soname change. -- Matthias Klose Wed, 25 May 2016 13:12:38

[Bug 1567940] Re: time displayed wrongly on production phone

** Changed in: canonical-devices-system-image Status: Confirmed => Fix Committed ** Changed in: canonical-devices-system-image Milestone: None => 11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1567940] Re: time displayed wrongly on production phone

So, I wrote a simple script to test my branch by looping through rebooting the phone and asking indicator-datetime what time it thought it was. * Wednesday's runs: 'automatic' time setting with London specified as the tzid * Thursday's runs: 'manual' time setting (as inspired by Ren's comment

[Bug 1567940] Re: time displayed wrongly on production phone

I tried both automatic and manual, made no difference until a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567940 Title: time displayed wrongly on production phone To manage

[Bug 1567940] Re: time displayed wrongly on production phone

I guess the issue comes from that on your phone the Date and Time is not defined as "Automatically" but "Manually". I remember I had this problem until I set the Date to "Automatically". This may help... -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1567940] Re: time displayed wrongly on production phone

Alan, if my guess in comment 5 is correct, it's a timing issue that will show up only occasionally after booting, depending on how soon indicator-datetime starts making bus calls compared to when some bus services are ready. Some code in the indicator was making bus calls on startup rather than

[Bug 1567940] Re: time displayed wrongly on production phone

it appears to have corrected itself after a reboot on my phone and I can't reproduce it now. Very strange! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567940 Title: time displayed wrongly on

[Bug 1567940] Re: time displayed wrongly on production phone

Looking over the indicator-datetime code I do see a startup timing bug that might be causing this and have a patch for that; however, I'm not able to reproduce this bug on my krillin. Under the 'startup timing bug' working theory I've tried rebooting 10x and still am not seeing this bug. I'll get

[Bug 1567940] Re: time displayed wrongly on production phone

** Branch linked: lp:~charlesk/indicator-datetime/always-get-initial- tzid-from-timedate1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567940 Title: time displayed wrongly on production phone To

[Bug 1567940] Re: time displayed wrongly on production phone

Thanks. I reproduced a similar for different issue on my krillin. The difference is that I get 3 different time for RTC, universal and local time. ** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Status:

[Bug 1567940] Re: time displayed wrongly on production phone

read: but* different -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567940 Title: time displayed wrongly on production phone To manage notifications about this bug go to: