Can confirm this behaviour too, since yesterday I think (I update every day). This behaviour was the “default”, no need to create another user. On a laptop with AMD + Nvidia
Possibly related posts:
- SDDM stuck at login - #4 by asterisk
- https://old.reddit.com/r/kde/comments/1g4tmg9/dual_monitor_login_not_working/
- https://forum.garudalinux.org/t/plymouth-plasma-and-dual-monitor-login-not-working/39744
possible kde bug tracking: https://bugs.kde.org/show_bug.cgi?id=494804
inxi -Fxxc0z
journalctl --no-hostname -k -b -0
journalctl --no-hostname -b -u sddm
journalctl --no-hostname -b -p3
wayland-session.log is empty
### /etc/sddm.conf.d/kde_settings.conf
[Autologin]
Relogin=false
Session=
User=
[General]
HaltCommand=/usr/bin/systemctl poweroff
RebootCommand=/usr/bin/systemctl reboot
[Theme]
Current=breeze
[Users]
MaximumUid=60513
MinimumUid=1000
### /etc/sddm.conf
[Autologin]
Session=plasma
from the pacman logs I can see that from the 14th qt got updated from 6.6 to 6.7 and then 6.8. On the 10th kde went from 6.1 to 6.2
edit:
kde 6.2.1 is availabe now, updating and will report if anything changes
edit 2:
the update did not fix it. I noticed the color of the reboot/logout etc icons in the second screen, the one with the non working login, is different from the main one, it’s greyish and looks a bit like the disabled state of buttons