A missing dot might indicate a previous startup failure which would be the real issue, but your description contradicts that by suggesting there is a dot. And now there is no dot?
I'm not sure what the problem description really is here, but these log messages look odd: oct. 01 10:25:56 i56400 systemd[4287]: Starting GNOME Shell on Wayland... oct. 01 10:25:56 i56400 systemd[4287]: Starting GNOME Shell on X11... oct. 01 10:25:56 i56400 systemd[4287]: [email protected]: Control process exited, code=exited, status=2/INVALIDARGUMENT oct. 01 10:25:56 i56400 systemd[4287]: [email protected]: Skipped due to 'exec-condition'. oct. 01 10:25:56 i56400 systemd[4287]: Condition check resulted in GNOME Shell on X11 being skipped. oct. 01 10:25:56 i56400 systemd[4287]: [email protected]: Scheduled restart job, restart counter is at 1. oct. 01 10:25:56 i56400 systemd[4287]: Stopped GNOME Shell on X11. oct. 01 10:25:56 i56400 systemd[4287]: Starting GNOME Shell on X11... ... oct. 01 10:25:56 i56400 systemd[4287]: Started GNOME Shell on X11. ... oct. 01 10:25:59 i56400 systemd[4287]: Started GNOME Shell on Wayland. ... I've seen the same in another bug recently. Maybe the desktop developers need to retest Nvidia-on-Wayland support to try and clarify what problems exist that look like this. -- 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/1945750 Title: [nvidia] gdm3 do not connect to the right session on 21.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
