GDM3 does not correctly memorize the Wayland choice for NVIDIA cards (driver 470) and randomly launches X11.

[MV]

GDM3 does not correctly memorize the Wayland choice for NVIDIA cards (driver 470) and randomly launches X11. The user must always select Wayland before logging if he wants to be sure to have a Wayland session.

[Daniel van Vugt (vanvugt)]

Sounds like the opposite of bug 1944581. Next time the problem happens please run:

  journalctl -b0 > journal.txt
  dpkg -l > packages.txt

and attach the resulting text files here.

Also, in future please use the 'ubuntu-bug' command to open new bugs.

[MV (mvidal)]

I rebooted after update and now I have in the list "ubuntu / ubuntu with Xorg" no dot at all but I connect to wayland as it seem to be the default now.

same when I close session and reopen it.

[Daniel van Vugt (vanvugt)]

The attached log shows that Wayland is being used (gnome-shell process 4441).

What makes you think it's not working?

[MV (mvidal)]

The dot, indicating the default is missing

[Daniel van Vugt (vanvugt)]

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=2/INVALIDARGUMENT
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.

[MV (mvidal)]

Sorry for the confusion, The list changed after I applied an update. After this update I logged with "ubuntu" (wayland) but the dot was still missing these past days. Yesterday I decided to select "ubuntu" to get the point and now the point remains in front of ubuntu.

So now everything is fine but it was confusing maybe this case can be close.

[Daniel van Vugt (vanvugt)]

OK, thanks.

[MV (mvidal)]

I rebooted now and without any reason (no update, no parameter modification) I logged again with Xorg. I left the session and the list is now : "ubuntu/ ubuntu with wayland". I guess there is a problem.

[MV (mvidal)]

journalctl with two loggings

[Daniel van Vugt (vanvugt)]

What you describe in comment #10 doesn't sound like a bug. What is it you think has gone wrong?

[MV (mvidal)]

I didn't want to log with Xorg as this last days I was logging without checking anything to wayland.

I'm playing with Schrodinger Cat

again, this morning I logged with Xorg when I checked Ubuntu with Wayland yesterday.

[MV (mvidal)]

I didn't want to log with Xorg as this last days I was logging without checking anything to wayland.

I'm playing with Schrodinger Cat

Again, this morning I logged with Xorg when I checked Ubuntu with Wayland yesterday. I left the session and saw that "Ubuntu with Wayland" was checked ( ????!!!???) I checked it again and now I'm with wayland.

[Daniel van Vugt (vanvugt)]

If the problem is that you get a session different to what you expected then please:

1. Reboot.

2. Log in.

3. If the session type is not what you expected then run:

   journalctl -b0 > wrongsession.txt

   and attach the resulting text file here.

4. If the session type is what you expected then goto 1.

[MV (mvidal)]

Here is what I got this morning as describe before. (last session I explicitly selected yesterday was Ubuntu for Wayland)

[Daniel van Vugt (vanvugt)]

That log seems to end with Gnome Shell using Wayland. It is gnome-shell process ID 7906. Is that not what you expected?

[MV (mvidal)]

The second login after logout is the one I explicitly select (knowing that it was already the default).

To be sure to have a wayland session I have to select it in the list whatever the default selection which is misleading and even sometimes absent (no point)

[Daniel van Vugt (vanvugt)]

That's why I suggested the steps in comment #15 -- to remove all ambiguity from multiple logins.

I've just retested Nvidia myself and did notice Wayland is never the default, and that does change the session names too, surprisingly. Is that the main issue this bug should be about?

Can you summarize the problem in one or two sentences because it would seem at least part of the original Bug Description above is no longer correct.

[MV (mvidal)]

the symptoms are multiple and I also had yours.

About the title, I'd say something like that :

GDM3 does not correctly memorize the Wayland choice for NVIDIA cards (driver 470) and randomly launches X11. The user must always select Wayland before logging if he wants to be sure to have a Wayland session

[Sebastien Bacher (seb128)]

Could you try if the update from https://bugs.launchpad.net/ubuntu/+source/gdm3/41~rc-0ubuntu2 resolves the issue for you?

[MV (mvidal)]

I updated and rebooted and now the list is "Ubuntu / Ubuntu with Wayland". The point was on "Ubuntu with Wayland" and so far it works well. As this bug is tricky I have to test further.

[MV (mvidal)]

I think this bug is fixed.