This issue is also present on Bionic. Is there a chance that the network
manager would be fixed in Bionic, as part of Ubuntu Pro?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1
Hi,
Here I found a better version of this script. It implements DHCPv6 and handles
directory and file creation better f.ex when IF goes down.
https://roll.urown.net/desktop/network/time-sync.html
Unfortunately the variable $DHCP6_NTP_SERVERS is always empty in my
case. Even I have correct NTP an
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.l
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchp
was the issue reported and discussed upstream yet? those scripts added
to the package sound like downstream workaround we will have to carry
and should be a backup plan if the issue can't be properly fixed
upstream. And even if a distro hack makes sense it would be better to
have it in Debian to re
Here is a networkd-dispatcher fix:
https://launchpad.net/~hellsworth/+archive/ubuntu/networkd-dispatcher/+build/22316215
And here is a network-manager fix:
https://launchpad.net/~hellsworth/+archive/ubuntu/network-manager/+build/22316944
Both should work, so please test the networkd-dispatcher fi
There is also an additional requirement. The package must install
successfully and replace an existing file that would have been created
manually (we had to ship the file on the image for the customer since we
don't have this fix in a package yet)
--
You received this bug notification because you
IMHO having the fix in network-dispatcher makes more sense.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1933828
Title:
NTP servers from DHCP are not propagated to timesyncd
I've got this setup between two vms, where the server vm is hosting
dnsmasq with ntp and the client synchronizes from the server (on a
private network). This issue of the timesync conf needing to be updated
exists in systemd-timesyncd too. But tackling the NetworkManager case as
this is the custome
@Seb this fix has to go to focal for a customer project and must land in
the dev release first.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1933828
Title:
NTP servers from
The bug is assigned and targetted to focal, it's import for the LTS but
we don't believe it should be a release issue for impish
** Tags removed: rls-ii-incoming
** Tags added: rls-ii-notfixing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
The server is set via a configuration file. The default config file is
/etc/systemd/timesyncd.conf and it can be overridden by dropping files in
/etc/systemd/timesyncd.conf.d/.
There is a pool of free ntp servers available on https://www.ntppool.org/en/.
To test this fix you also need a DHCP se
I tried to reproduce this, to test the fix, but I am stuck trying to figure out
how to manually set the ntp server. I can't see any difference between when the
vm (with no network) has this
/etc/NetworkManager/dispatcher.d/10-update-timesyncd file in place or not. I
think that's good but maybe
** Changed in: oem-priority
Assignee: (unassigned) => Cyrus Lien (cyruslien)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1933828
Title:
NTP servers from DHCP are not p
** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1933828
Title:
NTP servers from DHCP are not propagated to time
** Tags added: oem-priority originate-from-1933586 wenshan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1933828
Title:
NTP servers from DHCP are not propagated to timesyncd
** Also affects: network-manager (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu Focal)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu Focal)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
--
You received
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1933828
Title:
NTP servers from DHCP are not propagated to timesyncd
Status in network-manager p
** Summary changed:
- NTP servers from DCHP are not propagated to timesyncd
+ NTP servers from DHCP are not propagated to timesyncd
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
--
You received this bug notification because you are a membe
19 matches
Mail list logo