This bug was fixed in the package systemd-shim - 9-1bzr3
---
systemd-shim (9-1bzr3) wily; urgency=medium
* debian/patches/lp1390120.patch
- Cherrypicked: Use the ntp support for 'systemd-timesyncd.service'
too (LP: #1390120)
-- Ken VanDine ken.vand...@canonical.com
On Fri, May 22, 2015 at 03:01:43PM -, Pat McGowan wrote:
** Changed in: canonical-devices-system-image
Status: Confirmed = Fix Released
I'm not sure what that means but if it means that it's supposed to be
fixed then it's not yet. I only uploaded one piece to wily. I think
seb128 is
** Changed in: canonical-devices-system-image
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1390120
Title:
Manually
On Fri, May 22, 2015 at 04:18:50PM +0100, Iain Lane wrote:
On Fri, May 22, 2015 at 03:01:43PM -, Pat McGowan wrote:
** Changed in: canonical-devices-system-image
Status: Confirmed = Fix Released
I'm not sure what that means but if it means that it's supposed to be
fixed then
** Changed in: lxc-android-config (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: systemd-shim (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This bug was fixed in the package lxc-android-config - 0.223
---
lxc-android-config (0.223) vivid; urgency=medium
[ Oliver Grawert ]
* usr/bin/tethering: reloading config to get tethering working again
[Alfonso Sanchez-Beato]
* fix regression with NM setting DEVICE_IFACE to
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1390120
Title:
Manually
** Changed in: lxc-android-config (Ubuntu)
Importance: Undecided = Critical
** Changed in: lxc-android-config (Ubuntu)
Importance: Critical = High
** Changed in: lxc-android-config (Ubuntu)
Assignee: (unassigned) = Ken VanDine (ken-vandine)
** Changed in: systemd-shim (Ubuntu)
The bug isn't really about changing the time, it's about changing
automatic and manual. We've figured out that this fix is only part of
the problem. This works well if the device is read/write but it still
doesn't persist after reboot. We need to figure out where the daemon is
writing the state
I'm testing the silo and don't really understand what is supposed to
happen. I first set my timezone, and even though the setting is set to
Manual the time adjusts correctly to my current timezeone.
Seems like problem 1 is the default setting should be Automatic if it's
going to use that
** Also affects: systemd-shim (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd-shim (Ubuntu)
Status: New = Confirmed
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a
** Branch linked: lp:~ken-vandine/ubuntu/wily/systemd-shim/ntpfix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1390120
Title:
Manually set time and date reverts to
** Changed in: systemd-shim (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1390120
Title:
Manually set time and date reverts to
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Importance: Undecided = High
** Changed in: canonical-devices-system-image
Status: New = Confirmed
** Changed in: canonical-devices-system-image
Bumping importance on this
We should also decide on the proper default which I would assume to be
Automatically
** Changed in: ubuntu-system-settings (Ubuntu)
Importance: High = Critical
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) = Ken VanDine (ken-vandine)
It also reverts to 'automatic' after connecting to a wi-fi network (not
sure if part of this bug, or should raise as separate bug, but it's the
same behaviour issue)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Unsure what's going on there, but on my rtm bq device automatic doesn't
reverts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1390120
Title:
Manually set time and date
On krillin/vivid this is the opposite behaviour. Manual is set by
default after a fresh flash, if the user set it to Automatic and
reboot, it's back to Manual upon reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
On Thu, Feb 12, 2015 at 01:30:08PM -, Sebastien Bacher wrote:
@Martin, settings call org.freedesktop.timedate1 SetNTP(), so I guess
that panel is just doing nothing useful when selecting automatic update?
Can you verify this bug?
I first had to cherry-pick
@Martin, settings call org.freedesktop.timedate1 SetNTP(), so I guess
that panel is just doing nothing useful when selecting automatic update?
** Changed in: ubuntu-system-settings (Ubuntu)
Importance: Undecided = High
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
What kind of systemd interface is system-settings calling to
enable/disable automatic time? At the moment we install ntpdate, which
hooks itself into /etc/dhcp/dhclient-exit-hooks.d which isn't
configurable. timedatectl's set-ntp command is for a local NTP server
like ntpd or chronyd, but we don't
Thanks, settings call the systemd interface which changes the
configuration but that's not persistant. I looks like a ntpdate or
systemd request to store the configuration and restore it on boot
** Project changed: ubuntu-system-settings = systemd
** Project changed: systemd = systemd (Ubuntu)
23 matches
Mail list logo
