When I installed openSUSE Tumbleweed on my new laptop a year back I had chosen to automatically login to my user account (mostly because I chose encryption).
At any rate, after the Plasma 6 update I was expecting to be on Wayland, but the “Graphics Platform” remained X11 (which was more buggy for me). I haven’t had much interaction with SDDM previously, so I only figured out I had to log out and pick Plasma-Wayland as session more or less by accident from reading random comments about the upgrade in general. Then I realized that my selection didn’t persist and reverted back to X11 on reboots. I solved that by making a “session.conf” in sddm.d directory simply containing “[Autologin]” followed by “Session=plasmawayland.desktop”.
Maybe this topic will help someone out there, but I was wondering where else SDDM is configured because I couldn’t find any other configuration files or settings. I’d assume when you choose autologin upon installing this distro that autologin would be configured… somewhere? Just curious.
This led me to YaST Sysconfig Editor → Desktop → Window manager → DEFAULT_VM, which says it’s deprecated and to use update-alternatives --config default-xsession.desktop instead, which finally leads to…
:~ # update-alternatives --config default-xsession.desktop
There are 2 choices for the alternative default-xsession.desktop (providing /usr/share/xsessions/default.desktop).
Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/share/xsessions/plasma6.desktop 25 auto mode
1 /usr/share/xsessions/icewm-session.desktop 15 manual mode
2 /usr/share/xsessions/plasma6.desktop 25 manual mode
Press <enter> to keep the current choice[*], or type selection number:
I’ll try deleting my “session.conf” file and selecting 2 here, but this is looking like the correct way to do this, so thanks! Edit: Spoke too soon. Seems neither alternative gave me wayland…
The same patch that adds /etc/sysconfig/displaymanager support to SDDM also makes SDDM default to X11 session for auto-login ignoring any previous session remembered for this user. I do not know if it is intentional. I already described it on this forum and I believe more than once (so much about “helping someone out there”) and I repeat - someone who is affected by it should open bug report.