You are not logged in.
Steps to reproduce:
sudo systemctl disable sddm
[you will be locked out of the system if the problem happens]
update with kde-unstable active
reboot, login on the terminal
sudo systemctl start sddm
sddm login screen apears normal, but no mouse and no keyboard input work
power off button works, so I rebooted, removed the updates, and checked journalctl -I -u sddm
The only thing I got about an error was this:
Starting X11 session: "" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-oiqSuQ --theme /usr/share/sddm/themes/breeze"
Greeter session started successfully
Message received from greeter: Connect
Error from greeter session: "Process crashed"
Auth: sddm-helper (--socket /tmp/sddm-auth-9ea8c72f-15ad-44da-9fcd-763c7737b19c --id 2 --start /usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-oiqSuQ --theme /usr/share/sddm/themes/breeze --user sddm --greeter) crashed (exit code 1)
Error from greeter session: "Process crashed"
Auth: sddm-helper exited with 1
Greeter stopped. SDDM::Auth::HELPER_AUTH_ERRORfor now, I disabled the repo and ran pacman -Suu and everything is working
Last edited by aricaldeira (Yesterday 20:58:39)
Offline
Follow-up: kde-unstable is not the problem here, something in extra-staging is; made a quick test, disabling and reenabling the unstable, staging and testing repos in sequence
The problem happens even with stable sddm, when the packages now on extra-staging are installed:
extra-staging/fwupd 2.0.19-1 2.0.19-2 0,00 MiB
extra-staging/gst-libav 1.26.10-2 1.26.10-3 0,00 MiB
extra-staging/gst-plugins-bad 1.26.10-2 1.26.10-3 0,00 MiB
extra-staging/gst-plugins-bad-libs 1.26.10-2 1.26.10-3 0,00 MiB
extra-staging/gst-plugins-base 1.26.10-2 1.26.10-3 0,00 MiB
extra-staging/gst-plugins-base-libs 1.26.10-2 1.26.10-3 0,00 MiB
extra-staging/gst-plugins-good 1.26.10-2 1.26.10-3 0,00 MiB
extra-staging/gst-plugins-ugly 1.26.10-2 1.26.10-3 0,00 MiB
extra-staging/gstreamer 1.26.10-2 1.26.10-3 0,00 MiB
extra-staging/lua 5.4.8-2 5.5.0-1 0,07 MiB
extra-staging/lua-cassowary 2.3.2-2 2.3.2-3 0,00 MiB
extra-staging/lua-cldr 0.3.0-2 0.3.0-3 0,00 MiB
extra-staging/lua-cliargs 3.0.2-1 3.0.2-2 0,00 MiB
extra-staging/lua-expat 1.5.2-1 1.5.2-2 0,00 MiB
extra-staging/lua-filesystem 1.9.0-1 1.9.0-3 0,00 MiB
extra-staging/lua-fluent 0.2.0-3 0.2.0-4 0,00 MiB
extra-staging/lua-linenoise 0.9-9 0.9-10 0,00 MiB
extra-staging/lua-loadkit 1.1.0-2 1.1.0-3 0,00 MiB
extra-staging/lua-lpeg 1.1.0-4 1.1.0-5 0,00 MiB
extra-staging/lua-luaepnf 0.3-9 0.3-10 0,00 MiB
extra-staging/lua-luarepl 0.10-3 0.10-4 0,00 MiB
extra-staging/lua-luautf8 0.2.0-1 0.2.0-2 0,00 MiB
extra-staging/lua-penlight 1.15.0-1 1.15.0-3 0,00 MiB
extra-staging/lua-sec 2:1.3.2-2 2:1.3.2-3 0,00 MiB
extra-staging/lua-socket 1:3.1.0-1 1:3.1.0-2 0,00 MiB
extra-staging/lua-vstruct 2.2.0-1 2.2.0-2 0,00 MiB
extra-staging/lua-zlib 1:1.4-1 1:1.4-2 0,00 MiB
extra-staging/opencv 4.12.0-18 4.13.0-1 2,27 MiB
extra-staging/spectacle 1:6.5.4-1 1:6.5.4-2 0,00 MiBActive repos are kde-unstable, core-staging, core-testing, core, extra-testing, extra, everything works fine;
Offline
Disable staging repos. Those should never be enabled, and breakage is completely normal if you do.
Offline
Thanks!
So that you know, I've been working with all repos active, and daily updates, on my laptop, for quite some time, it's very rare I have any real issues, like this time.
I do this because I manage some servers with arch, with a policy of updating weekly, so I run a very unstable environment myself, so I can catch any possible problems before updating the servers.
Few things run on those servers, Postgres, Python (Odoo), and some other less important packages; that's how I handled the Python 3.14 update, dealing with the eventual recompiles and reinstalls first on my laptop; by the time the Python update went to the stable repos, I knew what to do, in what order etc. etc.
Offline