[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031406] Re: [MIR] libei
untu does carry a delta (going ahead of Debian) - Debian/Ubuntu update history is sporadic - Only a single upload in Ubuntu, not included in Debian - s390x dh_auto_test disabled in debian/rules https://gitlab.freedesktop.org/libinput/libei/-/issues/41 [Upstream red flags] OK: - no Errors during the build - no incautious use of malloc/sprintf (as far as we can check it) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside tests) - no use of user nobody - no use of setuid / setgid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case (user visible)? Problems: - warnings during the build (ignoring a few in the munit subproject): + src/util-sources.c:311:9: warning: ignoring return value of ‘read’ declared with attribute ‘warn_unused_result’ [-Wunused-result] + tools/ei-demo-client.c:102:9: warning: ignoring return value of ‘read’ declared with attribute ‘warn_unused_result’ [-Wunused-result] ** Bug watch added: gitlab.freedesktop.org/libinput/libei/-/issues #41 https://gitlab.freedesktop.org/libinput/libei/-/issues/41 ** Changed in: libei (Ubuntu) Assignee: Lukas Märdian (slyon) => Ubuntu Security Team (ubuntu-security) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop) ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2031406 Title: [MIR] libei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libei/+bug/2031406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
Thank you! The Netplan build seems to be fixed now. Removing the tag. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2026826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3047 https://gitlab.gnome.org/GNOME/glib/-/issues/3047 ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/-/issues/3047 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2026826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
** Description changed: Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in mantic-proposed. See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3 When I downgrade glib in my sbuild environment, everything works as expected: $ apt install libglib2.0-0=2.76.3-1ubuntu1 libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1 libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1 The build also works fine in Debian unstable, which is using glib2.0 2.74.6-2. Netplan is using plenty of GLib's keyfile functions (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to producing a different output with this newer release (some strange line breaks injected in the middle of a keyfile). + + + Example keyfile from the test_wifis.test_wifi_wowlan test, that should be generated by Netplan and the way it fails: + + Expected output: + ``` + [connection] + id=netplan-wl0-homenet + type=wifi + interface-name=wl0 + + [wifi] + wake-on-wlan=330 + ssid=homenet + mode=infrastructure + + [ipv4] + method=link-local + + [ipv6] + method=ignore + ``` + + Failure: + ``` + E AssertionError: '[con[88 chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n' + E [connection] + E id=netplan-wl0-homenet + E type=wifi + E interface-name=wl0 + E + E [wifi] + E wake-on-wlan=330 + E - + E ssid=homenet + E mode=infrastructure + E + + E [ipv4] + E method=link-local + E + E [ipv6] + E method=ignore + ``` ** Tags added: rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
I'm tagging this block-proposed to avoid this broken GLib to move into mantic-release. ** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026826] [NEW] glib2.0 (2.77.0 ) breaks Netplan build
Public bug reported: Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in mantic-proposed. See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3 When I downgrade glib in my sbuild environment, everything works as expected: $ apt install libglib2.0-0=2.76.3-1ubuntu1 libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1 libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1 The build also works fine in Debian unstable, which is using glib2.0 2.74.6-2. Netplan is using plenty of GLib's keyfile functions (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to producing a different output with this newer release (some strange line breaks injected in the middle of a keyfile). ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006483] [NEW] Fails autopkgtests when tested against fuse3 >= 3.13
Public bug reported: The autopkgtest in `tests/test-rofiles-fuse.sh` (executed via `gnome- desktop-testing-runner libostree/test-rofiles-fuse.sh.test`) fails to execute `setfattr -n user.foo -v bar mnt/anewfile-for-fuse` with the error message "setfattr: mnt/anewfile-for-fuse: Numerical result out of range". It's unclear if this is related to glibc, FUSE_USE_VERSION, kernel fuse protocol or another component. On Debian this specific test is skipped, due to missing the "capsh" binary (libcap2-bin) in the test env: ``` /usr/libexec/installed-tests/libostree/libtest.sh: line 688: capsh: command not found 1..0 # SKIP No cap_sys_admin in bounding set, can't use FUSE ``` The relevant log (inside an Ubuntu autopkgtest qemu runner) is provided here: ``` $ ../tests/test-rofiles-fuse.sh Copying gpghome to /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 checking for xattrs.../usr/bin/setfattr /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 # testlabel.txt: security.selinux: No such attribute Unable to retrieve SELinux label, assuming disabled /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 done checking for overlayfs whiteouts...done /usr/bin/setfattr d9793c4639f817fb95e3f1ae7a3f0571826db12a28baffaa3b3510f2ef0434a4 812152c68bb9c0b2a3bfcafeb5c4a4aa53827d8df5eeb755fe307f6a68f0febf fsck objects (20/20) [=] 100% object fsck of 2 commits completed successfully - no errors found. 1..12 a122802794e487785d14b58fe8969ab8716fd5c4c0ceed7de5c76061cd93f896 ok mount ok failed inplace mutation (open O_TRUNCATE) ok failed mutation chmod + chown setfattr: mnt/firstfile-link: Read-only file system ok new content setfattr: mnt/anewfile-for-fuse: Numerical result out of range Unexpected nonzero exit status 1 while running: setfattr -n user.foo -v bar mnt/anewfile-for-fuse gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent' gpg-connect-agent: waiting for the agent to come up ... (5s) gpg-connect-agent: connection to agent established OK closing connection ``` ** Affects: fuse3 (Ubuntu) Importance: Undecided Status: New ** Affects: ostree (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: fuse3 (Ubuntu) Importance: Undecided Status: New ** Description changed: The autopkgtest in `tests/test-rofiles-fuse.sh` (executed via `gnome- desktop-testing-runner libostree/test-rofiles-fuse.sh.test`) fails to execute `setfattr -n user.foo -v bar mnt/anewfile-for-fuse` with the error message "setfattr: mnt/anewfile-for-fuse: Numerical result out of range". It's unclear if this is related to glibc, FUSE_USE_VERSION, kernel fuse protocol or another component. - The relevant log is provided here: + On Debian this specific test is skipped, due to missing the "capsh" binary (libcap2-bin) in the test env: + ``` + /usr/libexec/installed-tests/libostree/libtest.sh: line 688: capsh: command not found + 1..0 # SKIP No cap_sys_admin in bounding set, can't use FUSE + ``` + + The relevant log (inside an Ubuntu autopkgtest qemu runner) is provided + here: ``` - $ ../tests/test-rofiles-fuse.sh + $ ../tests/test-rofiles-fuse.sh Copying gpghome to /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 checking for xattrs.../usr/bin/setfattr /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 # testlabel.txt: security.selinux: No such attribute Unable to retrieve SELinux label, assuming disabled /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 done checking for overlayfs whiteouts...done /usr/bin/setfattr d9793c4639f817fb95e3f1ae7a3f0571826db12a28baffaa3b3510f2ef0434a4 812152c68bb9c0b2a3bfcafeb5c4a4aa53827d8df5eeb755fe307f6a68f0febf fsck objects (20/20) [=] 100% object fsck of 2 commits completed successfully - no errors found. 1..12 a122802794e487785d14b58fe8969ab8716fd5c4c0ceed7de5c76061cd93f896 ok mount ok failed inplace mutation (open O_TRUNCATE) ok failed mutation chmod + chown setfattr: mnt/firstfile-link: Read-only file system ok new content setfattr: mnt/anewfile-for-fuse: Numerical result out of range Unexpected nonzero exit status 1 while running: setfattr -n user.foo -v bar mnt/anewfile-for-fuse gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent' gpg-connect-agent: waiting for the agent to come up ... (5s) gpg-connect-agent: connection to agent established OK closing connection ``` -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ostree in Ubuntu. https://bugs.launchpad.net/bugs/2006483 Title: Fails autopkgtests when tested against fuse3 >= 3.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/2006483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Changed in: lxd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Changed in: systemd (Ubuntu Impish) Status: Confirmed => Invalid ** Changed in: lxd (Ubuntu Impish) Status: New => Fix Committed ** Changed in: lxd (Ubuntu Impish) Assignee: (unassigned) => Lukas Märdian (slyon) ** Changed in: auto-package-testing Status: Incomplete => Invalid ** Changed in: dnsmasq (Ubuntu Impish) Status: Incomplete => Invalid ** Changed in: gdm3 (Ubuntu Impish) Status: Incomplete => Invalid ** Changed in: glibc (Ubuntu Impish) Status: Incomplete => Invalid ** Changed in: isc-dhcp (Ubuntu Impish) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
This should fix the problem: https://github.com/lxc/distrobuilder/pull/476 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Also affects: lxd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
So I can reproduce the problem even locally, using a simple: `autopkgtest systemd --test-name=boot-and-services -- lxd autopkgtest/ubuntu/impish/amd64` When logging into the (stalled) system, while it is waiting for its timeout I can see that eth0 gets configured, but then put in DOWN state. Therefore, systemd-networkd-wait-online.service (and thus network-wait- online.target) never get ready and the test times out waiting on "network-wait-online.target". A simple "networkctl up eth0" (inside the LXD container) during that 60s "timeout-wait" makes the test runner connect an finish the test successfully. The culprit for bringing down the interface seems to be "/run/systemd/system/network-device-down.service", but I have no idea where this files comes from or what it is used for. It's not part of any package. That service has a "Before=NetworkManager.service" dependency, that's why it only breaks tests making use of network-manager (boot-and- services & boot-smoke). The LXD/LXC stack seems to be somehow involved in creating that file: https://github.com/lxc/lxc-ci/pull/266 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Looks like I can at least reproduce the issue on an arm64 Canonistack machine, utilizing an armhf container: ubuntu@focal-arm64:~$ time autopkgtest systemd --test-name=boot-and-services -U -- lxd autopkgtest/ubuntu/impish/armhf [...] autopkgtest [15:59:21]: test boot-and-services: [--- lxc Created symlink /etc/systemd/system/default.target → /lib/systemd/system/graphical.target. bash: line 1: 3532 Killed /tmp/autopkgtest.OAYOpR/build.yrL/src/debian/tests/boot-and-services 2> >(tee -a /tmp/autopkgtest.OAYOpR/boot-and-services-stderr >&2) > >(tee -a /tmp/autopkgtest.OAYOpR/boot-and-services-stdout) autopkgtest [15:59:24]: test process requested reboot with marker boot1 Unexpected error: Traceback (most recent call last): File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 738, in mainloop command() File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 667, in command r = f(c, ce) File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 363, in cmd_reboot caller.hook_wait_reboot() File "/usr/bin/autopkgtest-virt-lxd", line 231, in hook_wait_reboot wait_booted() File "/usr/bin/autopkgtest-virt-lxd", line 104, in wait_booted VirtSubproc.check_exec(['lxc', 'exec', container_name, '--', 'sh', '-ec', '[ ! -d /run/systemd/system ] || systemctl start network-online.target'], timeout=60) File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 182, in check_exec (status, out, err) = execute_timeout(None, timeout, real_argv, File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 144, in execute_timeout (out, err) = sp.communicate(instr) File "/usr/lib/python3.8/subprocess.py", line 1014, in communicate stderr = self.stderr.read() File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 64, in alarm_handler raise Timeout() VirtSubproc.Timeout autopkgtest [16:01:18]: ERROR: testbed failure: unexpected eof from the testbed real8m29.354s user0m8.866s sys 0m8.141s Let's see what we can do about it. It looks like a dnsmasq (security-)update was pushed to Bionic++ on 2021-06-02 – about the same time that this test started failing on Bionic++ ... I wonder if this might somehow be related? ... need to further investigate. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-shell in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882532] [NEW] [Invalid] Testing apport snap handling...
Public bug reported: This can be ignored... just for testing as staging.launchpad.net is broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: i3 Date: Mon Jun 8 14:42:41 2020 InstallationDate: Installed on 2018-04-28 (772 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Snap: gnome-calculator 3.36.0+git9.96b95fd2 (stable) SnapSource: ubuntu/+source/gnome-calculator UpgradeStatus: Upgraded to focal on 2020-05-12 (26 days ago) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Assignee: Lukas Märdian (slyon) Status: Invalid ** Tags: amd64 apport-bug focal snap ** Changed in: gnome-calculator (Ubuntu) Status: New => Incomplete ** Changed in: gnome-calculator (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-calculator (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1882532 Title: [Invalid] Testing apport snap handling... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1882532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
