[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
I wonder whether my problem is this bug 1962036, or something else. Problem while upgrading impish to jammy: screen showing just background (no windows), moving/clicking mouse eliciting the "wait" cursor momentarily. Fixed by hard reset, boot to "recovery" console, and used: dpkg --configure -a apt dist-upgrade shutdown -r now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Fix Released Status in dbus source package in Jammy: Fix Released Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 288905] Re: /etc/init.d/ntp doesnt use ntpdate to ensure clocks are aligned before starting server.
The way I read man ntpd (on Debian wheezy), we could (should?) replace ntpdate by ntpd -q; and if we are going to run ntpd then ntpdate is unnecessary anyway. If we have (or are going to have) ntpd, then we should simply skip /etc/network/if-up.d/ntpdate; seeing how that depends on NTPSERVERS in /etc/ntp.conf or somesuch, I do not see that /etc/network/if-up.d/ntpdate is ever any use. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/288905 Title: /etc/init.d/ntp doesnt use ntpdate to ensure clocks are aligned before starting server. Status in ntp package in Ubuntu: Confirmed Bug description: Binary package hint: ntp Ubuntu: 8.04.1 ntp: 1:4.2.4p4+dfsg-3ubuntu2 Despite other comments on here that ntpdate should be run from ifup scripts there is still a fundamental issue. If due to failures such as #114505 not bringing up ntpd correctly if the clock drifts you have to ifdown, ifup an interface. On a major server thats just plain ridiculous...To fix the ntp daemon I have to pull down an ENTIRE network interface and stuff every service that is running on that interface - simply to fix ntpd. The alternative is that I have to either recognise and issue and then /etc/int.d/ntp stop ntpdate-debian /etc/init.d/ntp start again silly - because an /etc/init.d/ntp restart should work - the point of running NTP is it syncs. Therefore I propose that the /etc/init.d/ntp script is patched to include running of 'ntpdate-debian' during startup of the ntp server. This is a far more fail-safe method of working instead of forcing the admin to have to remember to run ntpdate-debian in case the clock has drifted excessively. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/288905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1125726] Re: boot-time race between /etc/network/if-up.d/ntpdate and /etc/init.d/ntp start
See also https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/288905 where I said: The way I read man ntpd (on Debian wheezy), we could (should?) replace ntpdate by ntpd -q; and if we are going to run ntpd then ntpdate is unnecessary anyway. If we have (or are going to have) ntpd, then we should simply skip /etc/network/if-up.d/ntpdate; seeing how that depends on NTPSERVERS in /etc/ntp.conf or somesuch, I do not see that /etc/network/if-up.d/ntpdate is ever any use. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1125726 Title: boot-time race between /etc/network/if-up.d/ntpdate and /etc/init.d/ntp start Status in ntp package in Ubuntu: Confirmed Bug description: We're seeing a race between if-up.d/ntpdate and the ntp startup script. 1) if-up.d/ntpdate starts. 2) if-up.d/ntpdate acquires the lock /var/lock/ntpdate-ifup. 3) if-up.d/ntpdate stops the ntp service [which isn't running anyway]. 4) if-up.d/ntpdate starts running ntpdate, which bids UDP *.ntp 5) /etc/init.d/rc 2 executes /etc/rc2.d/S20ntp start 6) /etc/init.d/ntp acquires the lock /var/lock/ntpdate. 7) /etc/init.d/ntp starts the ntp daemon. 8) The ntp daemon logs an error, complaining that it cannot bind UDP *.ntp. 9) if-up.d/ntpdate now starts the ntp service. The result is a weird churn, though ntpd does end up running at the end. Should these not be using the same lock file? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
