Comment 7 for bug 1945750
Revision history for this message
| Daniel van Vugt (vanvugt) wrote Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
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 address hidden>: Control process exited, code=exited, status=
oct. 01 10:25:56 i56400 systemd[4287]: <email address hidden>: 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 address hidden>: 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.