[Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest
This bug was fixed in the package systemd - 239-7ubuntu7 --- systemd (239-7ubuntu7) cosmic; urgency=medium * boot-and-services: skip gdm test, when gdm-x-session fails. Across all architectures, gdm fails to come up reliably since cosmic. (LP: #1790478) -- Dimitri John Ledkov Mon, 03 Sep 2018 16:33:00 +0100 ** Changed in: systemd (Ubuntu) Status: New => 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/1790478 Title: gdm3 in cosmic fails to start fully in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest
@Daniel: the latest gdm even in proposed that Dimitri and I can easily try is currently 3.29.91-1ubuntu2 -- 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/1790478 Title: gdm3 in cosmic fails to start fully in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest
...ubuntu7 completed tonight thanks! I tested 2 times from proposed in the local tester and working as expected now. Unfortunately the systemd upload itself failed at some of the flaky (boot and smoke) tests. But it seemed more like the VM it ran in would be dead. I retriggered the 4 tests (systemd, iproute2, cryptsetup, dbus) currently blocked on i386-systemd with appropriate triggers (currently triggers need: glibc, dbus, systemd). So in a few hours we know if those now resolve ... -- 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/1790478 Title: gdm3 in cosmic fails to start fully in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest
Try gdm version 3.29.92, which has a fix for some rather serious issues: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=fixed-in- gdm-3.29.92 -- 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/1790478 Title: gdm3 in cosmic fails to start fully in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest
I just found that further calls to $ sudo systemctl restart gdm Seem to alternate between good/bad state. Here is the log of one such bad restarts: http://paste.ubuntu.com/p/Dx7Sk3wDyx/ OTOH, the service could just in general not be restarable - so take this with a grain of salt -- 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/1790478 Title: gdm3 in cosmic fails to start fully in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest
I have found this to be locally reproducible with: $ autopkgtest --shell-fail --apt-upgrade --no-built-binaries --testname=boot-and-services --apt-pocket=proposed=src:systemd,src:dbus,src:iproute2,src:glibc systemd_239-7ubuntu6.dsc -- qemu --qemu-options='-cpu host' --qemu-command=qemu-system-i386 --cpus 8 --ram-size=4096 ~/autopkgtest-cosmic-i386.img What I see is that it really is failing. There are plenty of crashes in journal but those seem to be a swarm of red herring. The first start of gdm ends with X11 initializing and giving up like: /usr/lib/gdm3/gdm-x-session[pid]: dbus-daemon[1112]: [session uid=119 pid=1112] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=119 pid=1053 comm="/usr/lib/gdm3/gdm-x-session gnome-session --autost" label="unconfined") /usr/lib/gdm3/gdm-x-session[pid]: dbus-daemon[1112]: [session uid=119 pid=1112] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 /usr/lib/gdm3/gdm-x-session[pid]: Unable to register display with display manager But if you log in later and run "systemctl restart gdm" then all initializes as it is supposed to. It seems something yet unknown isn't available at early boot. I compared the X11 init of good/bad case but there is no difference (e.g. in detected HW), the first things that fails/differs is the org.freedesktop.systemd1 activation. But the boot start of gdm seems to be really (too early?) as halfway through I see: "Reached target Basic System" -- 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/1790478 Title: gdm3 in cosmic fails to start fully in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
