** Changed in: unity8 (Ubuntu)
Importance: Undecided => Critical
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Nick Dedekind (nick-dedekind)
** No longer affects: unity8
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to
Hi,
Just to be sure: does the patch is now landing is an image (I am using mako as
daily purpose, with channel devel on utopic image 203).
If it is suposing to be landed, then I can see this behavior's bug is
still here: always (and I mean always, everytime I need to check the
time) must open
@cm-t, there is a new bug about this: bug #1365530
--
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/1328646
Title:
Clock out of sync on resume
** Changed in: unity8
Status: In Progress = Fix Released
** Changed in: qmenumodel (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions:
** Changed in: unity8
Status: Triaged = In Progress
--
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/1328646
Title:
Clock out of sync
** Branch linked: lp:~nick-dedekind/unity8/lp1328646
--
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/1328646
Title:
Clock out of sync on
Marking this as Invalid for indicator-datetime as -- similar to
bug#1357311 -- the service is correctly pushing out menuitems and the
header label to the bus.
** Changed in: indicator-datetime (Ubuntu)
Status: Confirmed = Invalid
** Changed in: indicator-datetime
Status: New =
Just got this on my phone from letting it run over the weekend. Verified
the value passed over DBus is correct from the indicator:
$ gdbus call --session --dest com.canonical.indicator.datetime --object-path
/com/canonical/indicator/datetime --method org.gtk.Actions.Describe phone-header
((true,
** Changed in: unity8
Assignee: (unassigned) = Nick Dedekind (nick-dedekind)
--
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/1328646
Also see bug 1357307 which was introduced at the same time
--
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/1328646
Title:
Clock out of sync
Where does the greeter get its time from?
Indicator-datetime ultimately gets its time from a call to
g_date_time_new_now_local() + the system timezone, and (unless there's a
bug) is updated at least once per minute. But several people here
(jibel, ogra, more) are reporting the clock being /far/
Okay I've talked to mterry and he's confirmed that the greeter gets its
time and date from indicator-datetime. So this is good news of a sort,
it means the bug is probably only in datetime, rather than some larger
strangeness :)
** Changed in: indicator-datetime (Ubuntu)
Status: Confirmed
Here's the requested output:
http://paste.ubuntu.com/8057589/
What's weird... my indicator says 8:06 and the greeter 8:22 now... Both
over an hour out of sync.
After a greeter cycle the greeter came around to correct 9:45, panel
still off...
--
You received this bug notification because you
** Attachment added: system clock and indicator service say 8:30; panel and
greeter say 8:17
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4178916/+files/2014-08-15%2020.30.12.jpg
--
You received this bug notification because you are a member of DX
** Attachment added: greeter and indicator's ui says 8:17 -- but the system
clock and the timestamp that the indicator's published on the bus is 8:29
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4178915/+files/2014-08-15%2020.29.42.jpg
--
You
I'm seeing this bug in image 191 and found something interesting: the
datetime service is still pushing the right information to the bus, but
for some reason the panel and greeter aren't seeing it.
You can ask the datetime service what time it thinks it is by calling
this from phablet shell:
$
** Attachment added: partial unity8 log
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4178918/+files/unity8.log
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching
In the ~/.cache/upstart/unity8 log for the phone tested above, there are
several error warnings about a null property in
Panel/Indicators/DefaultIndicatorWidget.qml:76 and
(process:2451): GLib-GIO-CRITICAL **:
g_dbus_connection_signal_subscribe: assertion 'object_path == NULL ||
Lastly, it looks like indicator-datetime is continuing to correctly
publish the updated time when the minute changes.
You can reproduce this test on an affected system by running this from
phablet-shell:
$ dbus-monitor path=/com/canonical/indicator/datetime
Expected results: when the minute
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-datetime (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qmenumodel (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions:
** Changed in: indicator-datetime (Ubuntu)
Assignee: (unassigned) = Charles Kerr (charlesk)
--
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
The difference can be several hours. This morning, at 07:38 the time on
the phone was 04:09
--
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
On this photo mako shows 9:10 but it's 9:13 (both devices were in sync
at the beginning of the test)
** Attachment added: image20140807_0001.jpg
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171732/+files/image20140807_0001.jpg
--
You received this
9:14 on the watch, 9:14 on the clock of the phone and 9:10 in the
indicator (and the greeter before I unlocked it)
** Attachment added: image20140807_0002.jpg
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171734/+files/image20140807_0002.jpg
--
You
i must say that you are very lucky only getting teh clock being off by a few
minutes ...
*every* morning when i go to the landing meeting which starts at 10:30 for me
the notification for that particular meeting goes off at 10:40 or 10:45 ...
when the screen turns on with the notification
I can't reproduce this now, I see consistently synced clocks between
wizard, panel and clock app.
** Changed in: unity8
Status: New = Incomplete
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching
It happens to me all the time, your device have to be unplugged from
usb. Sometimes the time different is not a couple of minutes but like
half an hour.
** Changed in: unity8
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of DX
Packages,
Being away for a while and not having the phone plugged in all the time
this happened to me too all the time. But the panel seems to lag behind
too. It's in sync, but outdated. The time only updates when the next
minute update is triggered which in worst case leaves you with an
outdated clock for
Right, mine are constantly connected over USB so just don't suspend...
The issue seems to be that the indicator does not send the time updates
when device is suspended, *or* unity8 does not react to the updates it
does send.
If the latter, we just need to resync on wakeup, if the former, the
I'm saying this is critical as in normal phone usage your phone will be
8 hours behind for up to a minute in the morning...
** Changed in: unity8
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to
The proof! :)
The watch (time is set by GPS) indicates 23:17 and the phone indicates
23:16 in the indicator and the greeter
** Attachment added: 2216_2317.jpg
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171441/+files/2216_2317.jpg
--
You received
And on this photo, 1 minute later...
The time on the watch is 23:18 and on the phone it's 23:18 on the clock
and 23:16 in the indicator (and the greeter before I unlocked it)
The time on these 2 devices was in sync at the beginning of the test.
** Attachment added: 2316_2318.jpg
** Attachment removed: 2316_2318.jpg
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/+attachment/4171442/+files/2316_2318.jpg
** Attachment removed: 2216_2317.jpg
** Tags added: qa-daily-testing rtm14
--
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/1328646
Title:
Clock out of sync on resume from suspend
Confirmed on Utopic 161.
I unplugged the mako from USB, turned its screen off, and let it sit for
10 minutes next to a computer with a known-good clock. When I turned it
back on, its clock updated within one second from T-2m to T-1m -- that
is, it was just over a minute behind, after being idle
Note, given the behavior I saw, it's also possible that it was only
behind by about 40 seconds, and the second screen update wasn't related
to NTP or data from cell towers. The first (immediate) update could
have been the usual split second before the screen redraws on resume.
In any case, that's
Wow. So, when I tried again 13 minutes later, the clock was already 5
minutes behind. Apparently the speed isn't consistent.
It figured out the correct time again about 30 seconds later, but it
seems the onboard clock might be way off without help from the network
(cell or wifi).
--
You
Or maybe it's not the onboard clock, but just the display widget. If I
open the actual clock app, I can see two different times -- one in the
indicator, one in the app. So apparently the welcome time widget and
indicator widget just get out of sync with the system clock.
--
You received this
happens with me on image: r117
--
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/1328646
Title:
Clock out of sync on resume from suspend
I know that I was seeing some time-zone oddities when I tied the clock
to the phone_greeter menu model we got from the indicator (instead of
just phone). This was when the greeter was split out.
But after unsplitting, I haven't noticed any problems. But this
description makes it sound like the
41 matches
Mail list logo
