Hi Charles. I'm a core dev and I run Trusty on my laptop. Still
affected as of 2 months ago when I last traveled with that laptop. I
will test again with the latest software and post the results soon.
Excerpts from Charles Kerr's message of 2014-03-15 19:29:50 UTC:
> Thank you for taking the time
clint@clint-HP:~$ dconf dump /com/canonical/indicator/datetime/
[/]
locations=['UTC UTC', 'Pacific/Auckland Christchurch', 'Australia/Sydney
Sydney', 'America/Los_Angeles Los Angeles', 'Australia/Perth Perth',
'America/Denver Fort Collins']
timezone-name='America/Los_Angeles Los Angeles'
show-loc
Marking High/Triaged since I have confirmed it and experienced it.
** Changed in: indicator-datetime (Ubuntu)
Importance: Undecided => High
** Changed in: indicator-datetime (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of DX
Pack
John that is a completely different bug, please report it separately.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1247671
Title:
indicator
Public bug reported:
I recently travelled from my home area of Los Angeles to Hong Kong.
While the time zone correctly was changed in settings, the indicator
itself froze at the old time. killing the indicator-datetime-service
process resulted in the correct local time being displayed.
ProblemTyp
5 matches
Mail list logo
