I’m running Plasma with sddm and after updating when login, nothing happens. It still at the login screen. I can login to a virtual terminal and access the command line but posting logs is going to be tricky. I’ll probably have to use a live system and mount my filesystems.
I don’t think there was an update to sddm.
I don’t know what logs to post.
I’m wonder if I wait a couple days and update again if the problem will be fixed.
I’m making a silly guess but it proves right so many times…bet there was a kernel update and your Nvidia (making assumptions) is now broken. 50% of all issues seem to be NoVidia.
If so, it probably WILL be resolved in a couple of days.
I’m running an A8-6410 APU with AMD R5 Radeon Graphics.
It’s one of these weird little HP computers where they mounted I think it’s a mini ITX in a tower case. I got off eBay several years ago. It wasn’t what was advertised but I ended up keeping it. I put an SSD in it and USB 3 to gigabit ethernet adapter because it only had “fast” Ethernet. And I maxed out the ram to 16 GB.
It helps if you give the system config (inxi) when you post, then we’re not playing guessing games quite as much.
Weird, I run AMD graphics and everything is fine here with my Plasma.
Actually after I created the new user I found out something.
I can login to my original user if my mouse cursor is on my second monitor.
So I now my system is usable, but still acting a little strange.
I should be able to login no matter where my mouse cursor is.
If you want to fix it, or investigate, you have to do some work.
For example:
Inspect pacman log (the part from the last upgrade till the end) for error messages or unexpected end of the process.
less /var/log/pacman.log
Hit key End
Type /pacman and hit key Enter
Hit key N (capital N, with Shift+n), until you find a line which runs pacman -Syu, or equivalent (from a helper utility like yay).
You may copy the lines from there to the end of the log file, and post it (here, or in a paste-bin service). Or post the complete file, if you don’t mind.
Get journal messages
journalctl -b -u sddm
journalctl -b -p3
Get sddm log file
For SDDM in X11: $HOME/.local/share/sddm/xorg-session.log
For SDDM in Wayland: $HOME/.local/share/sddm/wayland-session.log
Get current sddm configuration (other than system/sddm default)
for Xconf in /etc/sddm.conf.d/*.conf /etc/sddm.conf ; do echo -e "\n### $Xconf" ; sudo cat "$Xconf"; done
By the way according to "About Systerm in Systemsettings I using Wayland, but
.local/share/sddm/wayland-session.log is empty
.local/share/sddm/xorg-session.log was last written to on July 24 and contains
kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: : No such file or directory
Error: Can not contact kdeinit5!
startkde: Starting up…
startkde: Shutting down…
startkde: Done.
I could probably post most of these here if I do 1 log pre message.
rick:~/ $ journalctl -b -u sddm
Oct 15 13:15:27 Pavillion550 systemd[1]: Started Simple Desktop Display Manager.
Oct 15 13:15:27 Pavillion550 sddm[686]: Initializing…
Oct 15 13:15:27 Pavillion550 sddm[686]: Starting…
Oct 15 13:15:27 Pavillion550 sddm[686]: Logind interface found
Oct 15 13:15:27 Pavillion550 sddm[686]: Adding new display…
Oct 15 13:15:27 Pavillion550 sddm[686]: Loaded empty theme configuration
Oct 15 13:15:27 Pavillion550 sddm[686]: Xauthority path: “/run/sddm/xauth_EWKymg”
Oct 15 13:15:27 Pavillion550 sddm[686]: Using VT 2
Oct 15 13:15:27 Pavillion550 sddm[686]: Display server starting…
Oct 15 13:15:27 Pavillion550 sddm[686]: Writing cookie to “/run/sddm/xauth_EWKymg”
Oct 15 13:15:27 Pavillion550 sddm[686]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_EWKymg -noreset -displayfd 16
Oct 15 13:15:29 Pavillion550 sddm[686]: Setting default cursor
Oct 15 13:15:29 Pavillion550 sddm[686]: Running display setup script “/usr/share/sddm/scripts/Xsetup”
Oct 15 13:15:29 Pavillion550 sddm[686]: Display server started.
Oct 15 13:15:29 Pavillion550 sddm[686]: Socket server starting…
Oct 15 13:15:29 Pavillion550 sddm[686]: Socket server started.
Oct 15 13:15:29 Pavillion550 sddm[686]: Loading theme configuration from “/usr/share/sddm/themes/breeze/theme.conf”
Oct 15 13:15:29 Pavillion550 sddm[686]: Greeter starting…
Oct 15 13:15:29 Pavillion550 sddm-helper[723]: [PAM] Starting…
Oct 15 13:15:29 Pavillion550 sddm-helper[723]: [PAM] Authenticating…
Oct 15 13:15:29 Pavillion550 sddm-helper[723]: [PAM] returning.
Oct 15 13:15:29 Pavillion550 sddm-helper[723]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=963) by (uid=0)
Oct 15 13:15:29 Pavillion550 sddm-helper[723]: pam_systemd(sddm-greeter:session): New sd-bus connection (system-bus-pam-systemd-723) opened.
Oct 15 13:15:30 Pavillion550 sddm-helper[723]: Writing cookie to “/tmp/xauth_ihzqeT”
Oct 15 13:15:30 Pavillion550 sddm-helper[723]: Starting X11 session: “” “/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-IGZTRo --theme /usr/share/sddm/themes/breeze”
Oct 15 13:15:30 Pavillion550 sddm[686]: Greeter session started successfully
Oct 15 13:15:30 Pavillion550 sddm[686]: Message received from greeter: Connect
Oct 15 13:15:57 Pavillion550 sddm[686]: Message received from greeter: Login
Oct 15 13:15:57 Pavillion550 sddm[686]: Reading from “/usr/share/wayland-sessions/plasma.desktop”
Oct 15 13:15:57 Pavillion550 sddm[686]: Session “/usr/share/wayland-sessions/plasma.desktop” selected, command: "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland>
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: [PAM] Starting…
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: [PAM] Authenticating…
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: pam_systemd_home(sddm:auth): New sd-bus connection (system-bus-pam-systemd-home-790) opened.
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: [PAM] Preparing to converse…
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: [PAM] Conversation with 1 messages
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: gkr-pam: unable to locate daemon control file
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: gkr-pam: stashed password to try later in open session
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: [PAM] returning.
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Oct 15 13:15:57 Pavillion550 sddm[686]: Authentication for user “rick” successful
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: pam_unix(sddm:session): session opened for user rick(uid=1000) by rick(uid=0)
Oct 15 13:15:57 Pavillion550 sddm-helper[790]: pam_systemd(sddm:session): New sd-bus connection (system-bus-pam-systemd-790) opened.
Oct 15 13:15:57 Pavillion550 sddm[686]: Auth: sddm-helper exited successfully
Oct 15 13:15:57 Pavillion550 sddm[686]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Oct 15 13:15:58 Pavillion550 sddm[686]: Session started true
lines 1-46/46 (END)
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
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
As tried in the other forum thread I uninstalled eos-plasma-sddm-config with
sudo pacman -R eos-plasma-sddm-config
and it fixed the issue. The log in screen theme gets removed and the old screen works fine, also the theme on the desktop does not change. Reinstalling the package triggers it again
Issue is not NVIDIA related, since eos-plasma-sddm-config is just 2 config files I checked the repo and there’s an old pull request which fixes it
If someone does not want to uninstall eos-plasma-sddm-config it’s possible to edit the file at
/etc/sddm.conf.d/kde_settings.conf
and paste the linked configuration. Please note that I only tried on my pc (but it shouldn’t be a big issue since you can just remove this file or uninstall eos-plasma-sddm-config)