Timezone gets reset on boot on xenial

Bug #1613977 reported by Michał Sawicz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Invalid
High
Michał Sawicz
indicator-datetime (Ubuntu)
Invalid
Low
Unassigned
unity8 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Steps:
* set a timezone in settings app
* reboot

Expected:
* time is correct and datetime indicator shows the timezone

Current:
* time is in UTC and datetime indicator shows UTC

$ system-image-cli -i
current build number: 1
device name: frieza
channel: ubuntu-touch/staging/ubuntu
last update: 2016-08-16 17:09:33
version version: 1
version ubuntu: 20160816
version device: 20160809.0
version custom: 20160816

$ cat /etc/timezone
Europe/Warsaw
$ date
Wed Aug 17 08:11:37 UTC 2016

Michał Sawicz (saviq)
Changed in canonical-devices-system-image:
milestone: none → xenial
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks but what desktop/device is that? is that on the phone? also the indicator doesn't set timezones that's done through the systemd helpers, is the system tz also incorrect or is it only a rendering issue in the indicator?

Changed in indicator-datetime (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Michał Sawicz (saviq) wrote :

Sorry, yes it's on the phone. I've added some details to the description.

description: updated
Revision history for this message
Michał Sawicz (saviq) wrote :

I'm not sure why the timezone isn't set correctly in the shell, but it's the same on vivid, so it does seem to be an indicator issue alone.

Revision history for this message
Michał Sawicz (saviq) wrote :

Oh but I also just realized the indicator sends dates in UTC I think, so it might be a unity8/Qt issue after all.

Changed in canonical-devices-system-image:
assignee: nobody → Michał Sawicz (saviq)
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Albert Astals Cid (aacid) wrote :

Was this xenial only or vivid too?

You mention xenial in the subject but then vivid on a comment.

I just tried on a vivid+overlay phone and it seemed to work fine, can you try again?

Changed in unity8 (Ubuntu):
status: New → Incomplete
Revision history for this message
Michał Sawicz (saviq) wrote :

Xenial only, my comment about vivid meant the indicator is the same in vivid, not that the issue is there in vivid.

Michał Sawicz (saviq)
Changed in canonical-devices-system-image:
status: Confirmed → Invalid
Changed in indicator-datetime (Ubuntu):
status: Incomplete → Invalid
Changed in unity8 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.