> But what is doing the asking? My best guess is a config in /etc/gdm3/custom.conf How that may have happened is that if mhalano had modified /etc/gdm3/custom.conf prior to the update they would have got a merge conflict on pkg upgrade and possibly resolved that incorrectly. They stated:
> I also will edit /etc/gdm3/custom.conf and edit to comment that line. > IIRC I got the error and then I edit it because I thought X11 was being > called and then I should force Wayland, even it was the default. so we're not seeing the configuration that was in-place for this behaviour to happen. I patched gdm to not accept a broken displayserver configuration anymore. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2122294 Title: gnome-session-init-worker crashes with SIGTRAP (Failed to start unit [email protected]: ...: Unit gnome- [email protected] not found.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2122294/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
