Wayland not available with proprietary Nvidia drivers even when nvidia-drm.modeset=1 is set

Bug #1887652 reported by Ian Johnson
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

With Ubuntu 20.04, GDM 3.34.1 (bundled with Focal), and the proprietary NVIDIA drivers, I am unable to use Wayland to login, and can only use XOrg. Debugging this a little, I found that wayland support is wholesale disabled when proprietary NVIDIA drivers are used by this rule: /lib/udev/rules.d/61-gdm.rules (coming from the gdm3 package), however it seems there may be more to this as well in upstream so this seems to affect mutter as well.

To be clear, my system only has NVIDIA graphics, I do not also have an Intel integrated GPU, so this is not a duplicate of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
tags: added: focal groovy
tags: added: nvidia nvidia-drm.modeset
Changed in mutter (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also something like this would probably help (to allow us to remove the udev rule):

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/625

Changed in gdm3 (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
summary: - wayland not available with proprietary nvidia drivers
+ Wayland not available with proprietary Nvidia drivers even when nvidia-
+ drm.modeset=1 is set
Changed in gdm3 (Ubuntu):
importance: Undecided → Low
Changed in mutter (Ubuntu):
importance: Undecided → Low
Changed in gdm3 (Ubuntu):
status: New → Triaged
Changed in mutter (Ubuntu):
status: New → Triaged
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Still true in 21.04. You need to comment out the nvidia rule in:

  /usr/lib/udev/rules.d/61-gdm.rules

tags: added: hirsute
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The rule to disable Wayland support on Nvidia is important right now, because it prevents bug 1705369 which hurt a lot of users. Although I have made an attempt to fix that properly (comment #3), upstream did not like it and currently prefers using 61-gdm.rules.

I'm hopeful a magical solution to this issue will appear in driver version 470 but have no evidence to support that. More likely I think I will need to revisit or patch https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/625

Changed in gdm3 (Ubuntu):
assignee: Daniel van Vugt (vanvugt) → nobody
Changed in mutter (Ubuntu):
assignee: Daniel van Vugt (vanvugt) → nobody
tags: removed: groovy
tags: added: impish
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
no longer affects: mutter (Ubuntu)
Changed in gdm3 (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The remaining problem is being tracked in bug 1946200

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.