[Desktop-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
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 and SNTP server addresses in my DHCPv6 options. I checked them with Wireshark. -- 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 OEM Priority Project: New Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Focal: Confirmed Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1557361] [NEW] package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 1.3.0-0ubun
Public bug reported: This is on a developer version of xenial. $ sudo apt-cache policy libjpeg-progs libjpeg-progs: Installiert: 8c-2ubuntu8 Installationskandidat: 1:9b-1 Versionstabelle: 1:9b-1 500 500 http://ftp.uni-stuttgart.de/ubuntu xenial/universe amd64 Packages *** 8c-2ubuntu8 100 100 /var/lib/dpkg/status What was expected? an upgrade or dist-upgrade should run to completion without errors What happened instead? $ sudo apt-get upgrade (...) Error: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Mar 14 22:58:05 2016 ErrorMessage: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 1.3.0-0ubuntu2 ist InstallationDate: Installed on 2015-01-26 (413 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.6 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 1.3.0-0ubuntu2 ist UpgradeStatus: Upgraded to xenial on 2016-03-05 (9 days ago) ** Affects: libjpeg8-empty (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1557361 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg- turbo-progs 1.3.0-0ubuntu2 ist Status in libjpeg8-empty package in Ubuntu: New Bug description: This is on a developer version of xenial. $ sudo apt-cache policy libjpeg-progs libjpeg-progs: Installiert: 8c-2ubuntu8 Installationskandidat: 1:9b-1 Versionstabelle: 1:9b-1 500 500 http://ftp.uni-stuttgart.de/ubuntu xenial/universe amd64 Packages *** 8c-2ubuntu8 100 100 /var/lib/dpkg/status What was expected? an upgrade or dist-upgrade should run to completion without errors What happened instead? $ sudo apt-get upgrade (...) Error: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Mar 14 22:58:05 2016 ErrorMessage: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 1.3.0-0ubuntu2 ist InstallationDate: Installed on 2015-01-26 (413 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.6 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 1.3.0-0ubuntu2 ist UpgradeStatus: Upgraded to xenial on 2016-03-05 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1557361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244138] [NEW] Run gnome-keyring-daemon using upstart
Public bug reported: After upgrading to LUbuntu 13.10, gnome-keyring-daemon (from the package gnome-keyring-3.8.2-0ubuntu3) was no longer started . Asking around in IRC suggested that the correct solution to the problem would be to upstartify gnome-keyring-daemon. So here I provide the attached upstart script. If added to the package at /usr/share/upstart/sessions/gnome-keyring, gnome-keyring-daemon should correctly be started without the need to modify the lxsession. ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Attachment added: "upstart script for gnome-keyring-daemon" https://bugs.launchpad.net/bugs/1244138/+attachment/3889568/+files/gnome-keyring-daemon.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1244138 Title: Run gnome-keyring-daemon using upstart Status in “gnome-keyring” package in Ubuntu: New Bug description: After upgrading to LUbuntu 13.10, gnome-keyring-daemon (from the package gnome-keyring-3.8.2-0ubuntu3) was no longer started . Asking around in IRC suggested that the correct solution to the problem would be to upstartify gnome-keyring-daemon. So here I provide the attached upstart script. If added to the package at /usr/share/upstart/sessions/gnome-keyring, gnome-keyring-daemon should correctly be started without the need to modify the lxsession. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1244138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
