Missing Wayland login option on NVIDIA systems

[Marcos Alano]

Impact
---------------------
Systems using Nvidia graphics drivers should have an option to use Wayland but Xorg should be the default.

Hybrid systems using Nvidia graphics drivers should use Wayland by default.

Test Case 1
-----------
Create a new user (since existing users can choose their own session).
Restart your system after applying the update.
Select your name on the login screen.
A gear button should appear in the lower right of the screen.
Click the gear button. Ubuntu should be selected.

If you are using a system with only an Nvidia graphics card (so your system is not a hybrid), there should be an Ubuntu on Wayland option.

Otherwise, there should be an Ubuntu on Xorg option.

Test Case 2
-----------
Also verify that the behavior stays the same for systems that don't have Nvidia graphics.

Create a new user (since existing users can choose their own session).
Restart your system after applying the update.
Select your name on the login screen.
A gear button should appear in the lower right of the screen.
Click the gear button. Ubuntu should be selected. There should also be an Ubuntu on Xorg option.

What Could Go Wrong
-------------------
Hybrid systems should actually be using the Intel graphics for to run GNOME Shell so that's why it should be safe to use Wayland by default.

There are some suspend & resume issues, an issue with gsync, etc. which is why Nvidia are requesting that we don't enable Wayland by default for systems that are only using the Nvidia graphics driver. We do still make it available in case someone really wants to try without needing to edit system files.

Before last week, we were actually using Wayland by default for Nvidia systems so this upload returns most systems back to that status quo.

Priority
--------
This is a high priority for the Desktop and OEM Teams and it's requested that this update be available as soon as possible after release.

The desktop live session defaults to Xorg not Wayland so this doesn't impact that session at all. We are not going to delay the release to get this fix on the Ubuntu 22.04 desktop ISO.

Original Bug Report
-------------------
I'm using Ubuntu 22.04 on a Dell G15 5511 laptop that have an NVIDIA 3060 GPU. I saw in the last update in the gdm3 package that Wayland will be disabled in machines with hybrid graphics.
The question is: In this laptop I can enable optimus to use Intel and sometimes NVIDIA or keep only on NVIDIA (I use this option). So even it's detected two GPUs the Intel one is unused.
I think the problem could extend for people with a desktop with an integrated intel GPU and a discrete NVIDIA GPU, since both will be present in the system.
So maybe will be necessary to check with more accuracy to check if there are two GPUs, but only one is being used or have a documented option to force the enablement of Wayland.

[Daniel van Vugt (vanvugt)]

We're working to restore Wayland support in bug 1968809.

[Marcos Alano (mhalano)]

As you can see in the screen attached, the reported GPU is NVIDIA because I set the always-on option in BIOS.

[Marcos Alano (mhalano)]

This screen show the firmware option related to hybrid graphics

[Marcos Alano (mhalano)]

I got the gdm3 package version 42.0-1ubuntu4 and still don't get Wayland. I troubleshot and found the problem in the file /lib/udev/rules.d/61-gdm.rules in the following lines:
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
If I comment that Wayland appears as an option in GDM.
I had to create a file /etc/modprobe.d/nvidia-hack.conf with the follow content:
options nvidia NVreg_PreserveVideoMemoryAllocations=1
This theoretically enable the option to preserve video memory allocations, but still getting the option as "1", still don't enable Wayland.

[Marcos Alano (mhalano)]

The preserve option enabled

[Marcos Alano (mhalano)]

The command executed right in the shell showing preserve option as 1

[Marcos Alano (mhalano)]

Even with all the steps for suspend/resume checked, I still don´t get Wayland support.

[Marcos Alano (mhalano)]

This patch implement these checks: https://salsa.debian.org/gnome-team/gdm/-/blob/ubuntu/master/debian/patches/data-Disable-wayland-on-nvidia-if-suspend-is-broken.patch

[Pirouette Cacahuète (lissyx)]

While this might sound as fishy, I hit the same problem, but my laptop is NOT with NVIDIA hardware ; it's a ThinkPad P14s Gen 2 AMD, with an AMD GPU. I had to reboot over the last few days and got no issue, until I rebooted one hour ago and got stuck on X11 instead of Wayland. After I found about that bug report and commented around the lines mentionned in comment #4, I could get back Wayland working.

Specifically, those:
> #### Check if suspend/resume services necessary for working wayland support is available
> ###TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
> ###TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia", GOTO="gdm_disable_wayland"
> ###IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 's/^/NVIDIA_/' /proc/driver/nvidia/params\""
> ###ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
> ###IMPORT{program}="/bin/sh -c 'echo NVIDIA_HIBERNATE=`systemctl is-enabled nvidia-hibernate`'"
> ###ENV{NVIDIA_HIBERNATE}!="enabled", GOTO="gdm_disable_wayland"
> ###IMPORT{program}="/bin/sh -c 'echo NVIDIA_RESUME=`systemctl is-enabled nvidia-resume`'"
> ###ENV{NVIDIA_RESUME}!="enabled", GOTO="gdm_disable_wayland"
> ###IMPORT{program}="/bin/sh -c 'echo NVIDIA_SUSPEND=`systemctl is-enabled nvidia-suspend`'"
> ###ENV{NVIDIA_SUSPEND}!="enabled", GOTO="gdm_disable_wayland"

[jan.t.neurer (neurer)]

Something's (jelly)fishy with todays 42.0-1ubuntu4 update for me too. X11 only, no Wayland option which has been working well for the last couple of weeks. I'm on a Thinkpad with Intel UHD Graphics 620, which at some point had a nVidia eGPU connected to it -- though not recently due to the several known external screen issues. Suggested workaround #4 and #9 fixed it for me, but I've also found myself having to set "WaylandEnable=true" in /etc/gdm3/custom.conf otherwise the dual-screens don't scale right.

[Kevin Keijzer (kkeijzer)]

For me 42.0-1ubuntu4 breaks Wayland as well on all my (Intel-only) machines.

[Jack Howarth (jwhowarth)]

On an X570 motherboard with 5600X processor and GTX 1050 graphics card, I was able to restore Wayland by simply commenting out the lines...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"

in /lib/udev/rules.d/61-gdm /lib/udev/rules.d/61-gdm. I would note that logging out back to gdm doesn't make these changes to /lib/udev/rules.d/61-gdm take effect. I always have to restart the system when I edit /lib/udev/rules.d/61-gdm.

[Jack Howarth (jwhowarth)]

The fact that a /etc/modprobe.d/nvidia-hack.conf file with 'options nvidia NVreg_PreserveVideoMemoryAllocations=1' doesn't bring back the Wayland option suggests that the line...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 's/^/NVIDIA_/' /proc/driver/nvidia/params\""

in /lib/udev/rules.d/61-gdm isn't parsing as expected. After rebooting with /etc/modprobe.d/nvidia-hack.conf in place, I find that executing...

/bin/sh -c "sed -e 's/: /=/g' -e 's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 's/^/NVIDIA_/' /proc/driver/nvidia/params"

produces 'NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1' however Wayland is only available if I precede the test for 'ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"' in /lib/udev/rules.d/61-gdm.rules with a manual assignment of 'ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}="1"'.

[Ghislain Vaillant (ghisvail)]

Same issue on a Dell XPS 15 laptop with NVIDIA GTX 1650 graphics. Wayland used to work since the initial beta release but stopped after the recent gdm3 package updates.

[Jack Howarth (jwhowarth)]

"gdm3 (42.0-1ubuntu6) jammy; urgency=medium

  * Fix Wayland no longer being available for everyone
    - Fix by adding a separate revert patch instead of trying to
      rebase the cherry-picked patches (LP: #1969243)
  * Please note that Wayland is not currently available for
    systems using the Nvidia graphics drivers because those drivers
    don't properly handle suspend and resuming from suspend. It is
    intended for those drivers to be fixed in a future stable release
    update for Ubuntu 22.04 LTS. See bug 1968929"

Does this imply that restoration of Wayland support for Nvidia will be treated like the upgrades to new major kernel releases and only occur after the 22.10 Ubuntu release?

[jan.t.neurer (neurer)]

Reverted all workarounds and updated to 42.0-1ubuntu6. Works for me.

[Jack Howarth (jwhowarth)]

How can we even know whether the Nvidia power mananagement support is broken or working if the Ubuntu Nvidia packaging never starts nvidia-hibernate.service, nvidia-powerd.service, nvidia-resume.service and nvidia-suspend.service like rpmfusion on Fedora? Of course, we would need a /etc/modprobe.d/nvidia-power-management.conf to get NVreg_PreserveVideoMemoryAllocations=1. However, I'm still unconvinced that the current check for NVreg_PreserveVideoMemoryAllocations=1 in 61-gdm.rules is really functional. In my hands, even though I had NVreg_PreserveVideoMemoryAllocations=1 present from addition of a /etc/modprobe.d/nvidia-power-management.conf contaiining....

options nvidia NVreg_PreserveVideoMemoryAllocations=1

the test...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"

in 61-gdm.rules never recognized its presence. It seems like the rule might not be properly parsing the escaped quotes.

Also, I looked at the Debian packaging for nvidia and I don't see any evidence that they have ever started those power management related services.

[Daniel van Vugt (vanvugt)]

I think NVreg_PreserveVideoMemoryAllocations sounds like a workaround for bug 1876632. That's not a new issue. Please tell me we're not disabling Wayland on Nvidia for an issue we've known about (and lived with) for years.

[Ghislain Vaillant (ghisvail)]

Updated gdm3 to 42.0-1ubuntu6, still no Wayland by default as it used to be (for a short span).

> * Please note that Wayland is not currently available for
    systems using the Nvidia graphics drivers because those drivers
    don't properly handle suspend and resuming from suspend. It is
    intended for those drivers to be fixed in a future stable release
    update for Ubuntu 22.04 LTS. See bug 1968929"

I am confused whether this means we are not getting "Wayland by default" back on laptops with hybrid graphics using NVIDIA.

[Daniel van Vugt (vanvugt)]

This seems to be a misunderstanding/overreaction to bug 1876632. We can live with that but should still try to fix it in future. The issue was further confused by Nvidia hybrid laptop users becoming involved these past few days thanks to bug 1969243.

Wayland support for Nvidia should be reinstated ASAP and the remaining issue then tracked in bug 1876632. We do not need to wait for Nvidia to fix a driver bug we've known about for years already.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1968929

[Daniel van Vugt (vanvugt)]

I think comments #22 and #24 probably belong in bug 1876632, not here.

[Daniel van Vugt (vanvugt)]

To make it clear we have two separate requirements I've opened bug 1969566 too.

[Henrik Harmsen (henrik-harmsen)]

I updated my 22.04 system today (with Nvidia proprietary drivers and a 3080 card). I added this file:

cat /etc/modprobe.d/nvidia-power-management.conf
options nvidia NVreg_PreserveVideoMemoryAllocations=1

Now both Wayland and suspend/resume seems to work for the first time ever. Without the above file, the system uses X11.

[Herman Resto (hresto)]

Henrik Harmsen's solution worked for me. I'll use this as a temporary solution until the official fix. Thanks!

[Daniel van Vugt (vanvugt)]

A fix was uploaded yesterday but it seemingly didn't make the release:

https://launchpadlibrarian.net/597672532/gdm3_42.0-1ubuntu7_source.changes

[Elias E. del Real (elias2022)]

I just did a fresh install of the official release of 22.04 LTS image today, and hit this problem. I see no gear icon, and it defaults to X11, with no option to select Wayland, whether I have just the NVIDIA GPU enabled, or both the Intel integrated GPU and the NVIDIA discrete GPU enabled in hybrid mode.

I had previously installed a nightly build of 22.04 LTS (beta) last week, and had the gear as an option, and was able to select and use Wayland.

[Daniel van Vugt (vanvugt)]

Yes it was a regression that only occurred in the past week :(

[Jimmys (jimmys-dimitrakopoulos)]

I am not certain this is related, but on a fresh install on my laptop with a gtx 1050 2gb, I installed the nvidia drivers. The 'intel graphics' option was greyed out on the nvidia prime selection and the wayland session was not available (gear missing).

I used the terminal command 'sudo prime-select intel'.

After reboot, the intel option is selected as well as greyed out and wayland is the default and running smoothly (actually there was some lag on X11, esp on boot with the dock, which is now gone).

[Daniel van Vugt (vanvugt)]

If you have a working Wayland option then you don't need to subscribe to this bug.

[Amardhruva (amaramardhruva)]

I too am affected by this bug.
System: Acer Predator Helios 300 Acer Predator PH315-53
GPU: Intel Integrated/ RTX 3060 Mobile

If I use prime-select intel then the wayland option appears and works fine.
If I use prime-select nvidia or prime-select on-demand then wayland option dissappears. I used to use the 22.04 beta few weeks back before nuking it to the 22.04 stable release and wayland used to work fine there with on-demand option.

One thing to note is that in Hybrid+wayland egl was not working properly which caused apps like mpv to crash(https://bugs.launchpad.net/egl-wayland/+bug/1968488). Im not sure if the issue is fixed rn.

[Steve Langasek (vorlon)]

Hello Marcos, or anyone else affected,

Accepted gdm3 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/42.0-1ubuntu7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Matias Piipari (mz2)]

I can confirm that with the proposed update on a previously impacted system (where Wayland was not available as an option) with an NVIDIA only GPU (RTX3090), "Test Case 1" behaves after the proposed update as expected: the Wayland option is made available, but default is "Ubuntu" (not "Ubuntu on Wayland").

[gutopardini (gutopardini)]

Ok, i can switch between Wayland and Xorg now and
My external DP monitor is Working after this fix
But i cant install nvidia Drivers via "Additional drivers" all versions is disabled
and all transitions, open menu, maximize, minimize have a terrible lag using wayland session

[叮当 (dingdang)]

I'm using a laptop with AMD and nvidia hybrid system. After installed the proposed upgrade I can use wayland session but xorg is still the default option.

[Zingam (registrirayme)]

I have a laptop with Intel+NVIDIA combo. I did a fresh install. Ubuntu uses Xorg and now it even feels choppier with more screen tearing than my previous 20.04 installation. I see none of the speed improvement claims from 22.04's release notes in the gnome session.

[Zingam (registrirayme)]

I use my laptop with an external monitor over HDMI so I hope this is a supported scenario.

[Jeremy Bícha (jbicha)]

My system doesn't have Nvidia graphics. I upgraded my gdm3 to 42.0-1ubuntu7 , restarted my computer and verified that my default session is still Ubuntu and there is an Ubuntu on Xorg login option. This verifies Test Case 2.

I don't think that comment 39 is sufficient to block this bug fix so I'm removing the verification-failed tag.

叮当 (dingdang), please open a new bug for your issue by running
ubuntu-bug gdm3

[Marcos Alano (mhalano)]

I have a Dell laptop that have an option in BIOS to always use the NVIDIA GPU instead of Intel/NVIDIA, and that the option I keep selected.
In the login screen, the gear shows "Ubuntu" and "Ubuntu on Wayland" options, so I think it's ok for non-hybrid machines until we fix all the problems.

[Nicholas Harvey (mobile-harvey)]

I can confirm on my Dell XPS15 9570 with hybrid Intel / NVIDIA graphics in on-demand mode that the proposed fix has allowed me to select Wayland in the log-in screen. Thanks.

[Rovano (rovano)]

Single Nvidia card in PCIE work well this patch.
First boot X session as default. Change to Wayland. Restart. Wayland persist.
Good job.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gdm3 - 42.0-1ubuntu7

---------------
gdm3 (42.0-1ubuntu7) jammy; urgency=medium

  [ Alberto Milone ]
  * Default to Wayland for hybrid systems with Nvidia graphics drivers.
    Default to Xorg but offer Wayland with the gear button on the login
    screen for non-hybrid systems with Nvidia graphics drivers. (LP: #1968929)

 -- Jeremy Bicha <email address hidden> Thu, 21 Apr 2022 06:32:09 -0400

[Steve Langasek (vorlon)]

The verification of the Stable Release Update for gdm3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Adam L (catfirmed)]

Hi! Same problem here. Clean install, Nvidia-510 + new updates. GTX 960M
Still cannot login Wayland sessions on 22.04 after the updates. Missing Wayland login option.

[Jeremy Bícha (jbicha)]

Adam L, did you restart your computer after making sure you had gdm3 42.0-1ubuntu7 installed?

Then follow the steps in Test Case 1 in this bug description (except for creating a new user).

If you still have an issue, please report a new bug since this bug is fixed. You can use the command

ubuntu-bug gdm3

[andyye (andyye03)]

Hi! I also have the same problem. It's a clean install, and I want to install the fix for gdm3. Can you please provide the instructions to do so?

[Daniel van Vugt (vanvugt)]

1. sudo apt update

2. sudo apt full-upgrade

3. Reboot

[sagu (sagudev)]

I have Ubuntu 22.04 and I did apt update and full-upgrade, but gdm3 is still on 42.0-1ubuntu6.

[Marcos Alano (mhalano)]

@sagu,

The version 42.0-1ubuntu7 is in jammy-updates repository.

[waffen (mlacunza)]

I just update today and I can run Wayland!! Thanks!
BUT... the option of night light is not working.

I'm using a Ci5 -10400F, nVidia Gtx 1650 with nvidia 510 driver.

How to reproduce: Configuration>Monitors>Night Light tab (I'm translating from Spanish)

don't work the temp selector or/and the on/off button.

[sagu (sagudev)]

$ sudo apt update
Dobi:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Zadetek:2 http://packages.microsoft.com/repos/code stable InRelease
Zadetek:3 http://si.archive.ubuntu.com/ubuntu jammy InRelease
Zadetek:4 http://si.archive.ubuntu.com/ubuntu jammy-updates InRelease
Zadetek:5 http://si.archive.ubuntu.com/ubuntu jammy-backports InRelease
Pridobljenih 110 kB v 1s (123 kB/s)
Branje seznama paketov ... Narejeno
Gradnja drevesa odvisnosti ... Narejeno
Branje podatkov o stanju ... Narejeno
All packages are up to date.

I'm using jimmy-updates repo.

[waffen (mlacunza)]

You need to run:
$ sudo apt upgrade

[Marcos Alano (mhalano)]

May be a phased rollout? Can you download and install directly from the repository?

[sagu (sagudev)]

On https://launchpad.net/ubuntu/jammy/amd64/gdm3/42.0-1ubuntu7 it says its phased rollout. Is there any way to force it?

EDIT: Found it here: https://askubuntu.com/questions/1246962/what-apt-configuration-file-should-the-never-include-phased-updates-flag-be-pl.
I can also confirm that night light is not working. Before I used Wayland with commenting out some gdm rules and night light worked normally. Before applying update I restored gdm rules and verify them.

[waffen (mlacunza)]

Today I already update to that version of gdm3, are your packages repo setup to Main server?

[sagu (sagudev)]

See my edit. And also Firefox when running with MOZ_ENABLE_WAYLAND=1 does not detect GPUs, so webgl does not work.

[Daniel van Vugt (vanvugt)]

sagu: Firefox should be discussed in bug 1970615

[Daniel van Vugt (vanvugt)]

waffen: The Night Light problem is being tracked in https://gitlab.gnome.org/GNOME/mutter/-/issues/290 but if you would like to open a new Launchpad bug about it too then that's fine.

[waffen (mlacunza)]

@Daniel: so is it a Gnome bug? not Ubuntu?

[Daniel van Vugt (vanvugt)]

We track GNOME bugs both upstream and here in Launchpad. Upstream is so that the developers can see the bugs, and here in Launchpad is so that we can track which Ubuntu versions are affected.

[Jesse Johnson (holocronweaver)]

To clarify, all future installs with hybrid Nvidia graphics will now default to Wayland? So users won't have to work around this issue by manually selecting Wayland in the log in screen? Cannot expect the average user to figure this out.

I am unclear why this bug was not rolled back once it was identified, and a fix that doesn't require manual intervention later released? Does the package release system not support rollbacks?

My experience:

Have a hybrid Nvidia laptop. After updating and rebooting, suddenly sleep caused laptop to lock up into a black screen requiring reboot, so effectively the laptop could not be used as a laptop. Upgraded to gdm3 42.0-1ubuntu7, which defaulted to X11 after reboot, had to log out and manually select Wayland which fixed suspend. Wayland selection persisted between reboots.

[Jesse Johnson (holocronweaver)]

Night Light was previously working on my hybrid Nvidia laptop before the recent changes that switched Wayland to X11. I manually switched back to Wayland, but now Night Light is not working.

Why are the changes that caused these bugs not being rolled back?

[Daniel van Vugt (vanvugt)]

Jesse,

It's complicated. There were too many intermediate versions (with additional important fixes like bug 1969097) in between to roll back over. The person in charge of that package does not have Nvidia hardware to test with either. Also this all happened only hours before the release so we had to move quickly. Rolling back was never really an option.

Please report a new bug for your "lock ups" if that's a problem.

As for the Night Light issue you mention, please create an additional new bug about it. It might be specific to Nvidia on Wayland (https://gitlab.gnome.org/GNOME/mutter/-/issues/290), or it might be specific to Intel 12th gen chips (bug 1967274), or it might be something else... I'm not aware of Night Light regressing in any case, unless you count the change from X11 to Wayland.

P.S. You may also be interested in tracking the list of nvidia-wayland bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-wayland

[waffen (mlacunza)]

Are you kidding me? So the guy in charge of the Nvidia issues don't have an Nvidia hardware?

[waffen (mlacunza)]

For the night light there's no fix for Wayland, you need to use x11

[Daniel van Vugt (vanvugt)]

> Are you kidding me? So the guy in charge of the Nvidia issues don't have an Nvidia hardware?

"gdm3" is not usually an Nvidia issue so does not usually require the involvement of people with Nvidia hardware. This was an unusual case. But as usual we all worked together and got it solved.

[Ralph Schmieder (ralph-schmieder)]

funny enough, I have the opposite issue, 22.04 w/ gdm3 42.0-1ubuntu7 installed and Nvidia 510 driver. Hardware is a Dell XPS 15 9510 w/ GeForce RTX 3050 Ti Laptop GPU.

When selecting the Nvidia "On-Demand" profile, I get both, Wayland and X11 in GDM. However, when I select "Performance Mode", X11 stops from working, it's not offered in the gear menu anymore. What's worse, even if I disable Wayland in /etc/gdm3/custom.conf, it seems like the X server simply crashes:

May 03 10:49:44 delle systemd[1]: Started GNOME Display Manager.
May 03 10:49:44 delle gdm-launch-environment][7269]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=126) by (uid=0)
May 03 10:49:45 delle gdm-launch-environment][7269]: pam_unix(gdm-launch-environment:session): session closed for user gdm
May 03 10:49:45 delle gdm-launch-environment][7269]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 03 10:49:45 delle gdm3[7263]: Gdm: GdmDisplay: Session never registered, failing
May 03 10:49:45 delle gdm3[7263]: Gdm: Child process -7287 was already dead.
May 03 10:49:45 delle gdm3[7263]: Gdm: GdmDisplay: Session never registered, failing
May 03 10:49:45 delle gdm3[7263]: Gdm: Child process -7287 was already dead.
May 03 11:01:10 delle systemd[1]: Stopping GNOME Display Manager...

Is this a separate / known issue?

[Daniel van Vugt (vanvugt)]

Certainly if a session type crashes then it will be removed from the login menu. Please report the crash in a new bug by following https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

It might be a known issue but which known issue we don't yet know.

[Zingam (registrirayme)]

Fix released but the state is New? What does this mean for the end users?

[Marcos Alano (mhalano)]

@registrirayme the state is new for the OEM Priority Project. It seems the fix was released for gdm3 package on Jammy release, so it should be all good.

[symdeb (symdeb)]

I see on the login screen "ubuntu" or "GNOME" both show X11 with loginctl (GEForce GT 610)
This is an older computurer but running Ubuntu 22.04 fine with an NVIDIA GF117 selected as the driver. NVIDIA driver-390. It does not have an Intel graphics controller.
Should the pre-release option still be enabled to get this fix ?

Linux H3 5.15.0-41-lowlatency #44-Ubuntu SMP PREEMPT Wed Jun 22 15:40:35 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy

[Daniel van Vugt (vanvugt)]

I can't remember how well Nvidia 390 supports Wayland. You might want to try adding a kernel parameter to enable it:

  nvidia-drm.modeset=1

[SunBear (sunbear-c22)]

Although a fix is mentioned as released, I still can't see Wayland used or even available for choosing in the GDM (The wheel at the bottom right of the GDM login screen only show Ubuntu and Gnome Classic but no Wayland). How do I get Wayland to be used instead of X11?

In Settings --> About, Window System states X11

System info:

$ uname -srmpo
Linux 5.15.0-47-generic x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy

$ nvidia-smi
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.141.03 Driver Version: 470.141.03 CUDA Version: 11.4 |
|-------------------------------+----------------------+----------------------+

$ gnome-shell
libmutter-Message: 00:26:16.788: Running GNOME Shell (using mutter 42.2) as a X11 window and compositing manager org.gnome.Shell already exists on bus and --replace not specified

[Daniel van Vugt (vanvugt)]

Since this bug has been closed for months, please open a new bug if you're still having problems:

  ubuntu-bug gdm3

[Nagle-animats (nagle-animats)]

This is the tracking bug for the followup from the previous failed attempt to fix the problem, which was https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/comments/37

Now this bug has been closed, although the problem is not fixed, as indicated by reports above.

Where is the followup bug for the followup bug for the failed attempt to fix the problem?

Additional discussion with more details: https://ubuntuforums.org/showthread.php?t=2486867
Screenshots there.

Did these fixes make it into Ubuntu 22.04.2 LTS?

[Daniel van Vugt (vanvugt)]

Discussion moved to bug 2020249.