I am using Manjaro GNOME. I wanted to use automatic1111, but it wasn’t recognising my graphics card (NVIDIA 1660 ti) and wasn’t proceeding to the next stage of installation (the terminal kept crashing when it got to a certain point), so Bing said that switching from wayland to x11 might fix it. I changed the /etc/gdm/custom.conf file to
# GDM configuration storage
[daemon]
AutomaticLoginEnable=False
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false
[security]
[xdmcp]
[chooser]
[debug]
# Uncomment the line below to turn on debugging
#Enable=true
and ran sudo systemctl restart gdm
When I did that, automatic1111 started working, in a sense (it still wouldn’t detect the models or loras I’d put in the models folder), but other stuff broke, in that swiping with three fingers no longer switched workspaces, the Ctrl-C Ctrl-V shortcuts stopped working, and Blender would crash upon opening. For those reasons, I wanted to switch back to wayland from x11, or even getting those features working with x11, I didn’t mind, but the former seemed easier.
I re-commented the line in the above file and ran sudo systemctl restart gdm again, but running echo $XDG_SESSION_TYPE returned x11 rather than wayland. The settings icon next to my username doesn’t let me switch between wayland and x11, but only GNOME and GNOME Classic.
Can you please help, if you can, with my predicament?
Out of curiosity, and I can’t think of why it would affect it - the
WaylandEnable=
is generally commented out instead of explicitly set. What happens if you put a#
in front of that line to comment it out again?That is what I did, that’s what didn’t work. Should I uncomment it and set it to true?
deleted by creator
If you haven’t already, it’s worth a shot!
That didn’t work, it’s still x11.
Hmm, I know at one point GNOME/GDM locked out Wayland for Nvidia cards - but that hasn’t been the case for a while (and possibly was distro specific).
Is there any output from:
cat /etc/udev/rules.d/61-gdm.rules cat /usr/lib/udev/rules.d/61-gdm.rules
~ cat /etc/udev/rules.d/61-gdm.rules ✔ cat: /etc/udev/rules.d/61-gdm.rules: No such file or directory ~ cat /usr/lib/udev/rules.d/61-gdm.rules 1 ✘ SUBSYSTEM!=“pci”, GOTO=“gdm_pci_device_end” ACTION!=“bind”, ACTION!=“add”, GOTO=“gdm_pci_device_end”
Hmm, so as long as you have 510 or above on the Nvidia driver you should not be getting blocked by that. I’m unfortunately not sure then.
Perhaps you could try installing
sddm
which is KDE’s display manager (the equivalent of GDM) and see if it shows the Wayland option?Pretty sure it doesn’t require the whole KDE suite, once it’s installed run:
sudo systemctl disable gdm && sudo systemctl enable sddm
and reboot, then you should get SDDM and can try to change the session type at the bottom left.Note that when using SDDM, you can’t lock your screen in Gnome since that is tied to GDM - you’ll get a notification saying that the screen lock isn’t available.
If SDDM doesn’t show it either, then somehow I think you’d be missing the actual session entry files? Not sure how that would happen though.
But I was on wayland before by default and I didn’t change any files? Unless automatic1111 changed them when I installed it. That’s the only thing I can think of.
Yeah that’s what I’m unsure about unfortunately. I’d be very surprised if that disabled Wayland. At one point, there was some remote desktop software that disabled Wayland silently, to get around the security restrictions of Wayland… But this project wouldn’t be bound by any Wayland restrictions as far as I can tell.
deleted by creator