You are not logged in.
I'd like to understand specifically what part of /usr/lib/udev/rules.d/61-gdm.rules is causing my system to disable Wayland support.
By default:
> echo $XDG_SESSION_TYPE
x11If I bypass the udev rules with
sudo ln -s /dev/null /etc/udev/rules.d/61-gdm.rulesI get:
> echo $XDG_SESSION_TYPE
waylandThe gdm.rules file contains lots of conditional code, and I'd like to understand specifically what part is causing Wayland to be disabled. I tried playing around with udevadm but could not figure it out.
I have a Nvidia 4090:
> nvidia-smi
Tue Nov 14 19:39:43 2023
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.29.02 Driver Version: 545.29.02 CUDA Version: 12.3 |
|-----------------------------------------+----------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+======================+======================|
| 0 NVIDIA GeForce RTX 4090 Off | 00000000:01:00.0 On | Off |
| 0% 46C P0 72W / 450W | 1121MiB / 24564MiB | 0% Default |
| | | N/A |
+-----------------------------------------+----------------------+----------------------+Offline
https://gitlab.gnome.org/GNOME/gdm/-/ra … type=heads
There're comments abotu every block of udev rules in plain english - what exactly do you not understand?
Hint: "# Above 510, prefer Wayland." means that's probably not relevant to you, but maybe one of the above blocks, not strcitly nvidia related, apply?
Also why do you want to mess around with that? The file controls whether you get wayland or X11, if you want to impact that, you just need to mask it.
Don't edit around in /usr/share, those edits will be gone with the next update.
Offline
> There're comments abotu every block of udev rules in plain english - what exactly do you not understand?
I'd like to see exactly what line is causing wayland to be skipped. Is there a way to turn on logging or run the script a 2nd time with logging enabled to see exactly what set of labels are executed?
> Also why do you want to mess around with that? The file controls whether you get wayland or X11, if you want to impact that, you just need to mask it.
That's what I did, but I want to understand WHY it's still preferring x11. The actual part of that script that disables wayland in my specific case is not clear.
Offline
That's what I did, but I want to understand WHY it's still preferring x11.
If you properly masked the file and still are denied wayland, the udev rules in there are obviously not relevant to your situation.
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stOffline
If I bypass the udev rules with
sudo ln -s /dev/null /etc/udev/rules.d/61-gdm.rules
I made an account just to thank you for this.
After installing `nvidia:open-dkms` drivers I ended up booting X11 and nvidia graphics card always, and what I wanted was just to use NVIDA for cuda, not graphics. So thank you!
Offline