You are not logged in.
If I undestood correctly I should just:
sudo systemctl disable sddm
sudo systemctl enable plasmalogin
But it only show a blank screen with a frozen input terminal _
I am lost on what I could try, this is my last attempt to use it, but just journalctl errors
mar 14 10:53:08 archlinux systemd[1]: Failed to start Virtual Console Setup.
mar 14 10:53:08 archlinux systemd[1]: Failed to start Virtual Console Setup.
mar 14 10:53:08 archlinux systemd-vconsole-setup[224]: /usr/bin/loadkeys failed with exit status 1.
mar 14 10:53:08 archlinux systemd-vconsole-setup[272]: /usr/bin/loadkeys failed with exit status 1.
mar 14 10:53:09 archlinux systemd-vconsole-setup[309]: /usr/bin/loadkeys failed with exit status 1.
mar 14 10:53:09 archlinux systemd[1]: Failed to start Virtual Console Setup.
mar 14 10:53:10 archlinux kernel: amdgpu: Overdrive is enabled, please disable it before reporting any bugs unrelated to overdrive.
mar 14 10:53:15 soul systemd-udevd[636]: /etc/udev/rules.d/50-qmk.rules:71 Failed to resolve group 'plugdev', ignoring: Unknown group
mar 14 10:53:15 soul kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x0018, size 0, write)
mar 14 10:53:15 soul kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x0019, size 0, write)
mar 14 10:53:15 soul kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001a, size 0, write)
mar 14 10:53:15 soul kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001b, size 0, write)
mar 14 10:53:15 soul kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001c, size 0, write)
mar 14 10:53:15 soul kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001d, size 0, write)
mar 14 10:53:15 soul kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001e, size 0, write)
mar 14 10:53:15 soul kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001f, size 0, write)
mar 14 10:53:15 soul kernel: i2c i2c-1: adapter quirk: no zero length (addr 0x0018, size 0, write)
mar 14 10:53:15 soul kernel: i2c i2c-1: adapter quirk: no zero length (addr 0x0019, size 0, write)
mar 14 10:53:20 soul bootctl[822]: Mount point '/efi' which backs the random seed file is world accessible, which is a security hole!
mar 14 10:53:20 soul bootctl[822]: Random seed file '/efi/loader/random-seed' is world accessible, which is a security hole!
mar 14 10:53:22 soul bluetoothd[858]: Failed to set default system config for hci0
mar 14 10:53:23 soul (systemd)[1033]: pam_access(systemd-user:account): access denied for user `plasmalogin' from `systemd-user'
mar 14 10:53:23 soul (systemd)[1033]: PAM PAM failed: Permission denied
mar 14 10:53:23 soul (systemd)[1033]: user@950.service: Failed to set up PAM session: Operation not permitted
mar 14 10:53:23 soul (systemd)[1033]: user@950.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
mar 14 10:53:23 soul systemd[1]: Failed to start User Manager for UID 950.
mar 14 10:53:57 soul dbus-broker-launch[853]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
~Last edited by Soultrigger (2026-03-24 20:14:26)
Offline
Thanks for your kindess, I tried to start the service, besides disabling and enabling it, but it didnt fix it.
I got it to work, it turns out my config was too restrictive:
/etc/security/access.conf
+:root:LOCAL
-:root:ALL
+:"myuser":LOCAL
+:(wheel):LOCAL
+:(adm):LOCAL
-:ALL:ALLSince I followed a bit of hardening secutiry from the install guide from some years ago, the fix for now was to add plasmalogin there:
+:root:LOCAL
-:root:ALL
+:"myuser":LOCAL
+:plasmalogin:LOCAL
+:(wheel):LOCAL
+:(adm):LOCAL
-:ALL:ALLNow I dont get it, so if any of you can explain it to me, SDDM was not added there, but I do have
/etc/pam.d/sddm
#%PAM-1.0
auth include system-login
-auth optional pam_gnome_keyring.so
-auth optional pam_kwallet5.so
account include system-login
password include system-login
-password optional pam_gnome_keyring.so use_authtok
session optional pam_keyinit.so force revoke
session include system-login
-session optional pam_gnome_keyring.so auto_start
-session optional pam_kwallet5.so auto_startSo in my mind if I created a file with that setup called /etc/pam.d/plasmalogin it would fix it without having to add plasmaloigin in /etc/security/access.conf. It didnt.
I dont recall if "pacman -S sddm" already creates that file or if I copied it from some model and created it there.
The question I leave for any kind soul is, why did SDDM worked without adding it to access.conf and how can I make plasmalogin work is a similar fashion?
The good thing is that I fixed most of those initialization errors with the help of AI, but it seems it cant really create a good explanation between sddm and plasmalogin when they are basically the same, and pam service that was blocking it from working.
Last edited by Soultrigger (2026-03-14 20:50:46)
Offline
Since I followed a bit of hardening secutiry from the install guide
I recommend not following random guides on the internet next time because they are sometimes incorrect or outdated, and today some of them turn out to be AI slop. If you do, record what you are doing and be able to reverse the changes.
How it feels to run shred/wipe in a COW system
Offline
Since I followed a bit of hardening secutiry from the install guide
I recommend not following random guides on the internet next time because they are sometimes incorrect or outdated, and today some of them turn out to be AI slop. If you do, record what you are doing and be able to reverse the changes.
Thanks mate for your kindness and it is a sound advice. But the guide I followed was the post install recommendations from Arch Wiki.
I left this open without a Solved status to see if someone could explain to me why SDDM worked without changing access.conf (pam) and Plasma Login didnt, so I will have to believe for now that SDDM is called as root, and even though Plasma Login is a fork might be called as normal user and thus needed the change @ access.conf.
Thanks all for all the insight and help.
Marked as Solved.
Offline