Calamares cannot enable autologin in SDDM for the Plasma Wayland session

[UriHerrera]

Describe the bug
Calamares cannot enable autologin in SDDM for the Plasma Wayland session if the option is selected during installation.

To Reproduce
Steps to reproduce the behavior:

1. Boot Live ISO
2. Login
3. Launch Calamares, navigate to the user creation module and enable auto-login and complete the installation
4. Reboot to the installed system; the user is not automatically logged in

Expected behavior
Users autologin to the session.

Desktop (please complete the following information):

• Nitrux 2.8.1
• Calamares 3.2.62

Additional context
I've no idea why Calamares cannot enable autologin in SDDM when the only session is Plasma Wayland (/usr/share/wayland-sessions/plasmawayland.desktop), but it has no problem enabling autologin when the default session is Plasma X11 (/usr/share/xsessions/plasma.desktop).

This problem has nothing to do with the immutability of the root partition/directory since, as I mentioned, Calamares can enable autologin when Plasma X11 is the default session.

My wild guess is that maybe Calamares expects the filename of the session file to be different.

---

Out of curiosity, I did the following. I linked the desktop file for the Wayland session to the desktop file for the X11 session. Indeed, the problem is that when Calamares sets up the autologin functionality during the installation, it does expect the Plasma session to be /usr/share/xsessions/plasma.desktop, hence why it does not work with Plasma Wayland or in our case, that Plasma Wayland is the only "valid" graphical session, because while the Plasma X11 session file remains in the root directory, the name is not plasma.desktop but orig.plasma.desktop.bak.

As noted in the screenshot of the VM, we can't consider doing this by default, even as a workaround.

---

Disclaimer: We do not develop the Calamares installer. Please create issues at its bug tracker here to request features or report problems.

---

It seems that when Calamares writes to the file /etc/sddm.conf and adds the Autologin details, the problem is that it's writing the session name wrong. It's adding plasma instead of plasmawayland.

So I guess the problem is that it doesn't know where to look for the Wayland session file.

---

To enable autologin, edit the file /etc/sddm.conf.d/kde_settings.conf in the following way.

• Where $USER is your username.
• Change Session=plasma to Session=plasmawayland to set the Plasma Wayland session as default when autologin.

[Autologin]
Relogin=true
Session=plasmawayland
User=$USER

[General]
HaltCommand=/usr/sbin/poweroff
RebootCommand=/usr/sbin/reboot

[Theme]
Current=nitrux-dark
CursorTheme=nitrux_snow_cursors

[Users]
MaximumUid=60000
MinimumUid=1000

And edit the file /etc/sddm.conf in the following way.

[General]
EnableHiDPI=true
InputMethod=

[UriHerrera]

Below is the moment where Calamares fails to enable autologin. As I noted before, it expects the session to be specifically plasma, and that is the name of the X11 session.

2023-08-15 - 20:50:23 [6]:     .. Job description from __doc__ "displaymanager" = "Configure display managers." 
2023-08-15 - 20:50:23 [2]: WARNING: [PYTHON JOB]: "The configured default desktop environment, plasma, can not be found." 
2023-08-15 - 20:50:23 [2]: boost::python::api::object CalamaresPython::GlobalStoragePythonWrapper::value(const string&) const
    WARNING: Unknown GS key autoLoginUser 
2023-08-15 - 20:50:23 [6]: [PYTHON JOB]: "Unsetting autologin." 

I wonder why that fails though.

[UriHerrera]

Fixed in Nitrux/calamares-settings-nitrux@bc26e7b