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?

  • JackGreenEarth@lemm.eeOPEnglish
    1·
    1 year ago

    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.

    • russjr08@outpost.zeuslink.netEnglish
      2·
      1 year ago

      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.