time displayed wrongly on production phone

Thanks for your report.

could you please run the following command on the device and paste the output:
$ timedatectl

thanks

OK, right now in the notification bar it is showing 13:33

phablet@ubuntu-phablet:~$ timedatectl
      Local time: Fri 2016-04-08 14:33:13 BST
  Universal time: Fri 2016-04-08 13:33:13 UTC
        RTC time: Fri 2016-04-08 13:33:08
       Time zone: Europe/London (BST, +0100)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: yes
 Last DST change: DST began at
                  Sun 2016-03-27 00:59:59 GMT
                  Sun 2016-03-27 02:00:00 BST
 Next DST change: DST ends (the clock jumps one hour backwards) at
                  Sun 2016-10-30 01:59:59 BST
                  Sun 2016-10-30 01:00:00 GMT

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.

read: but* different

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 the patch reviewed and put it in a silo so that other people experiencing this bug can see if it helps their phones.

it appears to have corrected itself after a reboot on my phone and I can't reproduce it now. Very strange!

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 looking for a bus owner to be ready and /then/ making the bus calls.

That doesn't explain the cities-in-blue-rather-than-orange issue in system settings though. Possibly two bugs for the price of one?

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...

I tried both automatic and manual, made no difference until a reboot.

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 #8) with America/Los_Angeles specified as the tzid

1000+ reboots later, I checked the outputs to see if they always increased over time or if there were outliers that jumped to the wrong timezone. The output looked like this:

> variant string " 7:40 AM"
> variant string " 7:42 AM"
> variant string " 7:43 AM"
> variant string " 7:44 AM"
> variant string " 7:45 AM"
> variant string " 7:47 AM"
> variant string " 7:48 AM"

For these two cases, at least, It looks like this branch is working.

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 <email address hidden> Wed, 25 May 2016 13:12:38 +0000