[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Changed in: dbus Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> The comment at https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992 suggests that disabling the DynamicUser= setting makes the service work again. Maybe that's worth a try, in order to get both problems solved? (i.e. shipping an override config for fwupd) > $cat /etc/systemd/system/fwupd-refresh.service.d/override.conf > [Service] > DynamicUser=no The whole point of using DynamicUser in this case was so that fwupdmgr didn't run as root when it reached out to the web to get data. Yes, certainly turning off DynamicUser in fwupd-refresh.service will solve the problem, but that is then a different threat vector. I think if turning off DynamicUser=1, then we probably need to also create a new service account for that systemd service to use. I'll open a new bug to move this discussion to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969976 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Quoting upstream systemd developers (https://github.com/systemd/systemd/issues/22737#issuecomment-1077682307): "We essentially traded one problem (lockup when starting services) for another (the failure described in this commit). I actually think that the lockup is worse. Here there is a simple solution: switch from dbus-daemon to dbus-broker. [...] A proper fix will most likely be to make all dbus calls asynchronous in systemd, but that is a lot of work and it's unclear when/if it'll happen. The regression is unfortunate, but I don't think we can fix it in reasonable time." So I wonder what's the best path forward in Ubuntu... if we revert, we'll re-introduce the lockup/timeout problem with dbus-daemon. If we keep the current version, fwupd-refresh.service is broken. The comment at https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992 suggests that disabling the DynamicUser= setting makes the service work again. Maybe that's worth a try, in order to get both problems solved? (i.e. shipping an override config for fwupd) $cat /etc/systemd/system/fwupd-refresh.service.d/override.conf [Service] DynamicUser=no -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 This appears to have caused a regression in fwupd in Ubuntu 20.04 with details at https://github.com/fwupd/fwupd/issues/3037 fwupd-refresh.service uses DynamicUser and now hits this upstream bug: https://github.com/systemd/systemd/issues/22737 ** Bug watch added: github.com/fwupd/fwupd/issues #3037 https://github.com/fwupd/fwupd/issues/3037 ** Bug watch added: github.com/systemd/systemd/issues #22737 https://github.com/systemd/systemd/issues/22737 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
This bug was fixed in the package systemd - 245.4-4ubuntu3.16 --- systemd (245.4-4ubuntu3.16) focal; urgency=medium [ Dan Streetman ] * d/p/lp1946388-sd-journal-don-t-check-namespaces-if-we-have-no-name.patch: Avoid journalctl segfault (LP: #1946388) [ Jeremy Szu ] * Add a allowlist to unblock intel-hid on new HP machines (LP: #1955997) Author: Jeremy Szu File: debian/patches/lp1955997-add-a-allowlist-to-unblock-intel-hid-on-HP-mach.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=88a859eaddb6c9a611fcbc44edab441aef4c4355 [ Nick Rosbrook ] * Prevent arguments from being overwritten with defaults at shutdown (LP: #1958284) File: debian/patches/lp1958284-core-move-reset_arguments-to-the-end-of-main-s-finish.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e61052bd1f20bcc54e7417542c6d445cf5040f56 [ Lukas Märdian ] * Fix deadlock between pid1 and dbus-daemon (LP: #1871538) Author: Lukas Märdian File: debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 -- Nick Rosbrook Wed, 23 Mar 2022 09:29:33 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
This bug was fixed in the package systemd - 248.3-1ubuntu8.5 --- systemd (248.3-1ubuntu8.5) impish; urgency=medium * debian/tests/boot-and-services: Ignore failed snap mount units in test_no_failed (LP: #1967576) systemd (248.3-1ubuntu8.4) impish; urgency=medium [ Lukas Märdian ] * Fix deadlock between pid1 and dbus-daemon (LP: #1871538) Author: Lukas Märdian File: debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f79535077473902bad911dc2652a2fff4066fa30 * Don't override Ubuntu's default sysctl values (LP: #1962038) Author: Lukas Märdian File: debian/patches/debian/UBUNTU-Don-t-override-Ubuntu-s-default-sysctl-values-LP-1962038.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3ba2764d8f77e616461c9722923f685fad79f8c6 systemd (248.3-1ubuntu8.3) impish; urgency=medium [ Jeremy Szu ] * Add a allowlist to unblock intel-hid on new HP machines (LP: #1955997) Author: Jeremy Szu File: debian/patches/lp1955997-add-a-allowlist-to-unblock-intel-hid-on-HP-mach.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=554d46e6a6ab80befd424ead7ffa8e6f993b5f66 -- Nick Rosbrook Fri, 01 Apr 2022 16:39:25 -0400 ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: verification-needed verification-needed-focal verification-needed-impish ** Tags added: verification-done verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I started 156 instances for both: * an impish image with systemd 248.3-1ubuntu8.5 * a focal image with systemd 245.4-4ubuntu3.16 In both images, I also removed the workaround in /etc/systemd/system/dbus.service.d (Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=1) to make sure I was really testing the fix. None of the instances shown any provisioning issue (cloud-init was always done withing 5min). This was the main symptom we were observing previously with this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish- proposed have been resolved. The regressions were caused either by (1) network/infrastructure issues and succeeded on retry, or by (2) unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added an autopkgtest change for systemd to ignore failed snap mount units which are caused by unrelated snapd issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal- proposed have been resolved. The regressions appear to have been related to recent autopkgtest infrastructure issues, and retrying the tests resolved the issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I can't test this reliably (as stated in the SRU description), but at least I can say I haven't seen it in the last 24h :-) I think this is on @gjolly to try to reproduce it in the mentioned azure test environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Hello Christian, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Hello Christian, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/417577 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Fixed also in systemd v250.4 and v249.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
This bug was fixed in the package systemd - 249.10-0ubuntu2 --- systemd (249.10-0ubuntu2) jammy; urgency=medium * Fix deadlock between pid1 and dbus-daemon (LP: #1871538) File: debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=100a7bfc2d0f82c3afbede04a022c655529cffac * Don't override Ubuntu's default sysctl values (LP: #1962038) File: debian/patches/debian/UBUNTU-Don-t-override-Ubuntu-s-default-sysctl-values-LP-1962038.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10cdb7da3539b3a3c3e619b470a75c83e46ef11 -- Lukas Märdian Tue, 08 Mar 2022 14:58:00 +0100 ** Changed in: systemd (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Changed in: systemd (Ubuntu Jammy) Status: New => In Progress ** Changed in: systemd (Ubuntu Jammy) Assignee: (unassigned) => Lukas Märdian (slyon) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Description changed: + [Impact] + + * There's currently a deadlock between PID 1 and dbus-daemon: in some + cases dbus-daemon will do NSS lookups (which are blocking) at the same + time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break + that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, + which will disable synchronously blocking varlink calls from nss-systemd + to PID 1. + + * This can lead to delayed boot times + + * It can also lead to dbus-daemon being killed/re-started, taking down + other services with it, like GDM, killing user sessions on the way (e.g. + on installing updates) + + [Test Plan] + + * This bug is really hard to reproduce, as can be seen from the multi- + year long discussion at https://github.com/systemd/systemd/issues/15316 + + * Canonical's CPC team has the ability to reproduce this issue (with a + relatively high probability) in their Azure test environment, due to the + specific setup they are using + + * So our test plan is to ask CPC (@gjolly) for confirmation if the + issue is fixed. + + [Where problems could occur] + + * This fix touches the communication between systemd and dbus daemon, + especially the NSS lookup, so if something is broken the (user-)name + resolution could be broken. + + * As a workaround dbus-daemon could be replaced by dbus-broker, which + never showed this issue or the behaviour could be changed back by using + the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: + + #/etc/systemd/system/dbus.service.d/override.conf + [Service] + Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 + + [Other Info] + + * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 + + + === Original Description === + + + This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash - rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 - - But that already was only triggered by a gnome restart that kicked of earlier: + But that already was only triggered by a gnome restart that kicked of + earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). - X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Groovy) ** No longer affects: systemd (Ubuntu Hirsute) ** Also affects: dbus (Ubuntu Jammy) Importance: High Status: Incomplete ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Changed in: dbus (Ubuntu Impish) Status: Incomplete => Invalid ** Changed in: dbus (Ubuntu Jammy) Status: Incomplete => Invalid ** Changed in: dbus (Ubuntu Groovy) Status: Incomplete => Invalid ** Changed in: dbus (Ubuntu Focal) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: dbus (Ubuntu Hirsute) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
This is now part of Azure's cloud images (focal to devel) and I can confirm that it fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
There is some news about this issue at systemd: https://github.com/systemd/systemd/issues/15316#issuecomment-1000842001 Could people try to place this systemd override config for dbus and observe if it avoids the issue? ``` $ cat /etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=1 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I'm still suspecting dbus to be at fault here. We might need to bisect dbus in order to find out more about this, but that is hard without a reliable reproducer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
FYI triggered again for me due to unattended upgrades. The time in the journal when things go down matches the unpack/configuee/install phase of - accountsservice:amd64 0.6.55-0ubuntu12~20.04.5 - libaccountsservice0:amd64 0.6.55-0ubuntu12~20.04.5 - dbus:amd64 1.12.16-2ubuntu2.1 I - again - had the usual suspect entries: systemd[1]: Starting Daily apt upgrade and clean activities... dbus-daemon[2266]: [system] Reloaded configuration dbus-daemon[2266]: Unknown group "power" in message bus configuration file systemd[1]: Reloading. systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated I didn't see anything in the log we didn't have before, but for completeness I'm attaching journal of the issue and a few hours before it ** Attachment added: "journal entries around the issues happening on unattended-upgrades" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+attachment/5541619/+files/fail-18Nov-6-24-07.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Addressed in FR-1460 ** Tags removed: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Merge proposal linked: https://code.launchpad.net/~vorlon/ubuntu-seeds/+git/platform/+merge/408418 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
An interesting observation I made is that all journal logs (in this LP bug and the upstream systemd bug) show the "polkit.service: Unexpected error response from GetNameOwner(): Connection terminated" message, in addition to a bunch of other "Connection terminated" errors from changing services across the different installations (NetworkManager.service, accounts-daemon.service, systemd- logind.service, ...). I've also seen logs (from Gauthier) where only polkit.service is failing. The polkit.service "Unexpected error response from GetNameOwner()" message is a log from systemd effectively telling us that systemd cannot reach org.freedesktop.PolicyKit1 on DBus. But the root cause for that must be that polkitd is not running (or dbus is somehow stuck in a deadlock, not responding anymore). This gives a new twist to this issue, as we might be searching for a phantom in (lib-)systemd... PolicyKit is using glib's gdbus implementation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Changed in: accountsservice (Ubuntu Groovy) Status: New => Invalid ** Changed in: accountsservice (Ubuntu Hirsute) Status: New => Invalid ** Changed in: gnome-shell (Ubuntu Groovy) Status: New => Invalid ** Changed in: gnome-shell (Ubuntu Hirsute) Status: New => Invalid ** Changed in: dbus (Ubuntu Groovy) Status: New => Incomplete ** Changed in: dbus (Ubuntu Hirsute) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: rls-ff-incoming rls-hh-incoming rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags added: fr-1460 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I filed an upstream bug with D-Bus: https://gitlab.freedesktop.org/dbus/dbus/-/issues/337 Hopefully a maintainer there will be able to give a better opinion as to what's going on here ** Bug watch added: gitlab.freedesktop.org/dbus/dbus/-/issues #337 https://gitlab.freedesktop.org/dbus/dbus/-/issues/337 ** Also affects: dbus via https://gitlab.freedesktop.org/dbus/dbus/-/issues/337 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Ok I will cook an other custom image and try to reproduce. Concerning this log line: Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=3ms, elapsed: 45129ms) Please note that during our first investigation with @slyon, we added this 9 in /etc/dbus-1/system-local.conf and this particular error disappeared. However the original issue ("Unexpected error response from GetNameOwner()" and slow critical-chain) was still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Thanks! Here's where I think the problem starts: Ok, let's authenticate to dbus: Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus bus-api-system: changing state AUTHENTICATING → HELLO ... Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus bus-api-system: changing state HELLO → RUNNING Right, systemd thinks it's done it at least. You can see a whole bunch of messages being returned, the connection is working. After a while (note this first timestamp jump; is that significant? looks to be waiting for udev to settle I think so maybe not; could be snapd related) we decide to do something with a Type=dbus unit: Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=1511 reply_cookie=0 signature=s error-name=n/a error-message=n/a Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetNameOwner cookie=1512 reply_cookie=0 signature=s error-name=n/a error-message=n/a And another timestamp jump, waiting for this timeout: Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=3ms, elapsed: 45129ms) Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.4 path=n/a interface=n/a member=n/a cookie=42 reply_cookie=1512 signature=s error-name=n/a error-message=n/a The dbus-daemon didn't think that the connection was authenticated. The last message AFAICS received on the bus connection was: Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=Reload cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Reloading. No smoking gun yet, at least not to me. But interesting that the last thing which happened successfully was reloading. Can we have another go please, with these changes vs. an upstream clean image? - LogLevel=debug in /etc/systemd/system.conf - Using the dbus 1.12.20-2ubuntu1+ppa1 from ppa:ci-train-ppa-service/4587. This dbus is just the one from impish backported to hirsute with verbose debugging turned on. And then attach the full `journalctl -b ` which will probably be quite large. :-) Maybe we'll get some information out of the dbus side to say what it thinks goes wrong with the connection. ** Please note ** The "connection has not authenticated" string does not appear in the earlier logs from Christian or Steve. It could be that there are two bugs here, with similar symptoms that systemd loses its connection to the system bus. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Also, systemd is actually reloaded by cloud-init. In cloud-init logs, I can read: 2021-06-16 08:54:51,608 - subp.py[DEBUG]: Running command ['systemctl', 'daemon-reload'] with allowed return codes [0] (shell=False, capture=True) 2021-06-16 08:54:51,953 - cc_mounts.py[DEBUG]: Activate mounts: PASS:systemctl daemon-reload 2021-06-16 08:54:51,953 - handlers.py[DEBUG]: finish: init-network/config-mounts: SUCCESS: config-mounts ran successfully -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
@laney I built a custom image with system logs level set to debug and I was able to reproduce the issue. You can find the logs attached. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/+attachment/5505001/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Also affects: dbus (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags added: rls-ff-incoming rls-hh-incoming ** Also affects: dbus (Ubuntu Impish) Importance: High Status: Incomplete ** Also affects: gnome-shell (Ubuntu Impish) Importance: Undecided Status: Invalid ** Also affects: accountsservice (Ubuntu Impish) Importance: Undecided Status: Invalid ** Also affects: dbus (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Groovy) Importance: Undecided Status: New ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
That's interesting actually. I thought this was an interaction between reloading dbus-daemon and daemon-reloading systems at the same time. But in this cloud case, I don't think dbus is being reloaded, is it? It's going to be next to impossible for me to look into this in detail without being able to reproduce it or getting a bit more debug information. Maybe you could crank up the system log level and try to reproduce this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I seems that we are seeing this issue on Azure with Ubuntu >=20.04. The CPC team is running a series of tests before publishing images, those tests spin up ~50 instances in Azure and usually one of them is having this issue. You can find the system logs of a failing instance here: https://pastebin.ubuntu.com/p/WC4M7JdTGk/ in which you can read the following: Jun 3 06:57:12 alan-focal-base-uuisspbroykxijgbixkk systemd[1]: accounts-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jun 3 06:57:12 alan-focal-base-uuisspbroykxijgbixkk systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated Jun 3 06:57:12 alan-focal-base-uuisspbroykxijgbixkk systemd[1]: polkit.service: Unexpected error response from GetNameOwner(): Connection terminated I built a custom hirsute image with dbus-broker installed and I was unable to reproduce the issue with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Oh.. I wasn't really aware of that (-1 = all) and it looked so similar. Right, so we still somehow need to find a proper reproducer... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Yeah, sorry, I don't think that's a reproducer for the bug. You killed dbus, gdm and everything else, and they obligingly died on you. :) My feeling is that this bug is about a deadlock that somehow happens when dbus and/or systemd are reloaded, possibly at the same time. It looks like dbus stops responding to systemd, and so when it calls GetNameOwner() to be able to watch type=dbus units, it gets no reply and then decides to kill all type=dbus units, which is a lot of things. If that's right, it's most likely to be a dbus bug that it can get into this state. But I'm personally at a bit of a loss as to how to approach it without being able to reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
kill(-1, SIGINT) kills all processes on the system with SIGINT, so this is hardly surprising. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Well, more correctly -1 means to all processes you can send to, and if you're root, well it's everyone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
By chance (while developing some netplan code), I seem to have found a reproducer for this bug... I don't know what is going on, but calling the 'Trigger' method from the attached 'dbus.c' file will kill the GDM session in a reproducible way. The invalid `kill(-1, SIGINT);` of line 21, seems to somehow crash the whole DBus/GDM and other services. So there must be some problem inside DBus's error handling, which is somehow triggered during the updates. * WARNING: calling the Trigger method via busctl will kill your GDM session * * compile: gcc -o out dbus.c `pkg-config --cflags --libs libsystemd glib-2.0` * execute: sudo ./out * trigger: sudo busctl call io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan Trigger ** Attachment added: "dbus.c" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+attachment/5414222/+files/dbus.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
@Dimitri desktop isn't working on it at this point, unsure how to figure out where the issue is exactly but it sounds like it could be either dbus or systemd which are owned by foundations -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Hm, so is desktop working on this? Have we figured out at all what is happening? Or just the general symptoms that dbus seems to be non- responsive and then everything goes bad? ** Changed in: dbus (Ubuntu) Status: Confirmed => Incomplete ** Changed in: dbus (Ubuntu Focal) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I've a similar issue on Groovy. I got it 2 days in a row after my daily package update. Reverting the machine to a state before the upgrade and re-upgrading the same packages doesn't reproduce the issue. However, when it worked with the same package update the message "Unexpected error response from GetNameOwner()" is not present in the logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The last two updates went smooth for me, not triggering it. I'm still too afraid to "just update while working" as I did in the past since it could drag things down thou :-/ I was feeling like this could be solved, but reading that Steve is also affected I'm worried that I might just not hit the same race/trigger by accident. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Changed in: systemd Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Bug watch added: github.com/systemd/systemd/issues #15316 https://github.com/systemd/systemd/issues/15316 ** Also affects: systemd via https://github.com/systemd/systemd/issues/15316 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I also hit this again in focal on 2020-06-25, with an update to systemd 245.4-4ubuntu3.1; I had previously updated dbus to 1.12.16-2ubuntu2.1 on 2020-06-17 without event. It's still an issue at least with updates to systemd in focal. Similar messages end up in the journal: Jun 25 13:04:55 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:04:55 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:04:55 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:04:55 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:05:10 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:05:10 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:05:10 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:05:10 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:05:10 kryten dbus-daemon[1541]: Unknown group "power" in message bus configuration file Jun 25 13:05:10 kryten systemd[1]: Reloading. Jun 25 13:05:11 kryten systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Jun 25 13:05:11 kryten systemd[1]: /lib/systemd/system/fancontrol.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fancontrol.pid → /run/fancontrol.pid; please update the unit file accordingly. Jun 25 13:05:36 kryten systemd[1]: We couldn't coldplug machine-qemu\x2d1\x2dkeybase\x2dbionic\x2damd64.scope, proceeding anyway: Connection timed out Jun 25 13:05:36 kryten dbus-daemon[1541]: [system] Reloaded configuration Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=switcheroo-control comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=polkit comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=colord comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 25 13:05:36 kryten systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jun 25 13:05:36 kryten ModemManager[1689]: Caught signal, shutting down... Jun 25 13:05:36 kryten thermald[1605]: [WARN]Terminating ... Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 25 13:05:36 kryten audit[1541]: USER_AVC pid=1541 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.9" mask="receive" pid=4082 label="bitlbee" pe> exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=accounts-daemon comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 25 13:05:36 kryten systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Jun 25 13:05:36 kryten bluetoothd[1536]: Terminating Jun 25 13:05:36 kryten systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Jun 25 13:05:36 kryten avahi-daemon[1535]: Got SIGTERM, quitting. Jun 25 13:05:36 kryten systemd[1]:
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
[Expired for dbus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dbus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
[Expired for dbus (Ubuntu Focal) because there has been no activity for 60 days.] ** Changed in: dbus (Ubuntu Focal) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I hit that again today on an upgrade. Network manager didn't come up again. Mai 20 11:04:46 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9491] caught SIGTERM, shutting down normally. Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9504] dhcp4 (enp0s31f6): canceled DHCP transaction Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9504] dhcp4 (enp0s31f6): state changed extended -> done Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9504] device (enp0s31f6): DHCPv4: trying to acquire a new lease within 90 seconds Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9733] dhcp4 (wlp4s0): canceled DHCP transaction Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9812] dhcp4 (wlp4s0): state changed bound -> done Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9813] device (wlp4s0): DHCPv4: trying to acquire a new lease within 90 seconds Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9817] device (p2p-dev-wlp4s0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed') Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9825] device (strswanbr2-nic): released from master device strswanbr2 Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9829] device (strswanbr1-nic): released from master device strswanbr1 Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9831] device (veth47e5): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0047] device (virbr0-nic): released from master device virbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0050] device (vethcc7405c8): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0069] device (vetha09a9db4): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0077] device (veth754add92): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0094] device (vethc060f004): released from master device virbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0101] device (veth3152ecc9): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0109] device (vethb6dd0569): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1008] device (virbr0): bridge port vnet1 was detached Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1025] manager: NetworkManager state is now CONNECTED_SITE Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1030] device (virbr0): bridge port vnet0 was detached Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1629] exiting (success) Mai 20 11:04:47 Keschdeichel systemd[1]: NetworkManager.service: Succeeded. Mai 20 11:04:48 Keschdeichel nm-openvpn[847263]: SIGTERM[hard,] received, process exiting $ systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2020-05-20 11:04:47 CEST; 15min ago Docs: man:NetworkManager(8) Main PID: 1330 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 38269) Memory: 12.2M CGroup: /system.slice/NetworkManager.service But that still isn't the root cause. And before this plenty of things failed on GetNameOwner() in that sense it is similar to the former occurance. Mai 20 11:03:56 Keschdeichel systemd[1]: Reloading. Mai 20 11:03:56 Keschdeichel systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run> Mai 20 11:04:11 Keschdeichel tracker-store[976018]: OK Mai 20 11:04:11 Keschdeichel systemd[18845]: tracker-store.service: Succeeded. Mai 20 11:04:21 Keschdeichel systemd[1]: We couldn't coldplug machine-qemu\x2d13\x2dfocal.scope, proceeding anyway: Connection timed out Mai 20 11:04:46 Keschdeichel systemd[1]: We couldn't coldplug machine-qemu\x2d11\x2dbionic.scope, proceeding anyway: Connection timed out Mai 20 11:04:46 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags added: id-5e988df7fb344884f67bc04f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Also affects: dbus (Ubuntu Focal) Importance: High Status: Incomplete ** Also affects: gnome-shell (Ubuntu Focal) Importance: Undecided Status: Invalid ** Also affects: accountsservice (Ubuntu Focal) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Oh, and I have no crash files in /var/crash/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Hi, I had a similar crash this morning upgrading focal, after trying to get unattended-upgrades to stop spinning on missing focal-security apt list files. In this case, I don't use gnome-shell as my desktop environment, but it still tore down my entire desktop environment and caused gdm3 to respawn. I've attached the journalctl log from when I started apt upgrade to when I successfully re-logged into my i3 session. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+attachment/5349957/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Sure @seb128 - I'll let you know if it happens again (as I did a cleaning-reboot now). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs