Finally fixed the issue as I noticed it kept coming back every time I rebooted my computer.
When using development containers (devcontainers) with VsCode, VsCode has a default-enabled setting under Preferences >> Settings >> Dev >> Containers >> "Mount Wayland Socket". This attempts to bind the wayland socket when starting the container. This way GUI apps run in a (most- likely) headless container will launch using your host wayland session. If the container is also configured to "auto-restart", it will come up when the docker daemon comes up at boot time. The container is beating GDM to the Wayland socket and so GDM fails to bind to it as it's already in use. Disabling either "auto-restart" or the VsCode Wayland bind settings should fix the issue. -- 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/2149849 Title: Wayland session fails to start. gnome-shell SIGTRAP: WL: bind() failed with error: Address already in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2149849/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
