Arch Linux

tsuritsuritsuri

Member

Registered: 2024-06-14

Posts: 2

[SOLVED] SDDM crashing on shutdown/reboot

Hey there! Just installed Arch on my everyday use laptop this last Thursday, been enjoying it a lot. I migrated completely from Windows, so it's not a dual boot. I accidentally screwed up my /home directory mounting a partition of my secondary HDD there accidentally, and in my very short Arch Linux experience, opted for doing a fresh install again. Everything worked nice, the exact same as before. However, since Saturday night I've been running into this particular issue that I think might have to do with SDDM. Login works fine, I've never had any issue with it. When I try to do "shutdown now" or "reboot", though... *Sometimes* it works fine, but most of the times the screen freezes (it doesn't go black) and I can't do anything at all. Touchpad, mouse, keyboard, everything is dead (which makes sense, since I can see in the log how they are successfully disconnected before the crash occurs). In top of that, the light in my caps lock starts blinking indefinitely, which makes me think it might even be a kernel panic or something related. Every single time it happens I have to shut it down manually with the button, so I'm not really liking this. My laptop was in battery conservation mode, so the battery was always around 55-60%, but after one of these episodes it suddenly was at 100% and the mode was in normal charging which just makes no sense at all (because the battery actually lasted long, making me think it was fully charged all along?).

Lenovo Ideapad Gaming 3 15ARH05,
AMD Ryzen 7 4800H with integrated graphics and an NVIDIA 1650 Ti with propietary drivers (installed in the archinstall process)
DE: Plasma 6.0.5
WM: kwin
Kernel: 6.9.5-arch1-1

And here is the log, from where I opened my terminal (Alacritty) to type the shutdown now command to where it crashed and I forced the shut down with the button:

Jun 18 00:30:48 archlinux systemd[728]: Started Alacritty - Terminal.
Jun 18 00:30:48 archlinux xdg-desktop-portal-kde[1064]:5mxdp-kde-settings: Namespace  "org.gnome.desktop.wm.preferences"  is not supported
Jun 18 00:30:50 archlinux systemd-logind[591]: The system will power off now!
Jun 18 00:30:50 archlinux systemd-logind[591]: System is poweringdown.e--
Jun 18 00:30:50 archlinux systemd[1]: Stopping Session 2 of User tsuri...
Jun 18 00:30:50 archlinux systemd[1]: Removed slice Slice /system/dbus-:1.2-org.kde.kded.smart.
Jun 18 00:30:50 archlinux bluetoothd[590]: Terminating
Jun 18 00:30:50 archlinux systemd[1]: Removed slice Slice /system/dbus-:1.2-org.kde.powerdevil.backlighthelper.
Jun 18 00:30:50 archlinux systemd[1]: Removed slice Slice /system/dbus-:1.2-org.kde.powerdevil.chargethresholdhelper.
Jun 18 00:30:50 archlinux systemd[1]: Removed slice Slice /system/dbus-:1.2-org.kde.powerdevil.discretegpuhelper.
Jun 18 00:30:50 archlinux systemd[1]: Removed slice Slice /system/getty.
Jun 18 00:30:50 archlinux systemd[1]: Removed slice Slice /system/modprobe.
Jun 18 00:30:50 archlinux systemd[1]: Stopped target Bluetooth Support.
Jun 18 00:30:50 archlinux systemd[1]: Stopped target Graphical Interface.
Jun 18 00:30:50 archlinux systemd[1]: Stopped target Multi-User System.
Jun 18 00:30:50 archlinux systemd[1]: Stopped target Login Prompts.
Jun 18 00:30:50 archlinux systemd[1]: Stopped target Sound Card.
Jun 18 00:30:50 archlinux systemd[1]: Stopped target Timer Units.
Jun 18 00:30:50 archlinux systemd[1]: archlinux-keyring-wkd-sync.timer: Deactivated successfully.
Jun 18 00:30:50 archlinux systemd[1]: Stopped Refresh existing PGP keys of archlinux-keyring regularly.
Jun 18 00:30:50 archlinux systemd[1]: shadow.timer: Deactivated successfully.
Jun 18 00:30:50 archlinux systemd[1]: Stopped Daily verification of password and group files.
Jun 18 00:30:50 archlinux systemd[1]: systemd-tmpfiles-clean.timer: Deactivated successfully.
Jun 18 00:30:50 archlinux systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Jun 18 00:30:50 archlinux systemd[1]: Stopped target System Time Set.
Jun 18 00:30:50 archlinux systemd[1]: systemd-rfkill.socket: Deactivated successfully.
Jun 18 00:30:50 archlinux systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jun 18 00:30:50 archlinux sddm[641]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Jun 18 00:30:50 archlinux systemd[1]: Stopping Bluetooth service...
Jun 18 00:30:50 archlinux sddm[641]: Auth: sddm-helper (--socket /tmp/sddm-auth-723b89a9-e372-49e9-bfc6-35a1e1dc0164 --id 1 --start /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland --user tsuri) crashed (exit code 1)e--
Jun 18 00:30:50 archlinux sddm[641]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Jun 18 00:30:50 archlinux sddm[641]: Auth: sddm-helper exited with 1

It doesn't seem to be an SSD problem, although at startup it did say something like "FAT-fs (nvme0n1p1) Volume was not properly unmounted. Some data may be corrupt. Please run fsck" but I think it is because of the forced manual shutdown so it might not be related to the actual cause. Also, I'm confused because the sddm-helper part says "--id 1 --start /usr....", which makes me think it's actually starting the process instead of carrying out the shutdown...? I don't know.

If you need any additional info I'll try to send it right away. Thanks!

Last edited by tsuritsuritsuri (2024-06-23 19:13:53)

Derp

Member

Registered: 2024-06-21

Posts: 2

Re: [SOLVED] SDDM crashing on shutdown/reboot

I'm having the same issue. Reboot and shutdown sometimes work, and sometimes doesn't. Using the reboot/shutdown buttons in KDE, the buttons in SDDM or the reboot / shutdown -r now commands make no difference.
Anecdotally from what i've seen it's after a system update that it hangs. Or well.. it shuts down but doesn't initiate a reboot. It just locks the screen and any peripherals. Which sort of makes sense since it has gone through the shutdown process.
I see the sddm-helper crash as well, but by the looks of it it's just how sddm shuts down now. The helper close through sigterm, systemd kills the sddm user session and the greeter goes: "What? We died? Must be auth error.".
As for the question about --start, that just shows what arguments sddm was started with, presumably on boot.

A weird find is that both clean reboots and dirty ones look the same in journalctl. So i'm really at a loss as to where to look next.

Dirty

Jun 21 20:03:39 assbox systemd[1]: Reached target System Shutdown.
Jun 21 20:03:39 assbox systemd[1]: Reached target Late Shutdown Services.
Jun 21 20:03:39 assbox systemd[1]: systemd-reboot.service: Deactivated successfully.
Jun 21 20:03:39 assbox systemd[1]: Finished System Reboot.
Jun 21 20:03:39 assbox systemd[1]: Reached target System Reboot.
Jun 21 20:03:39 assbox systemd[1]: Shutting down.
Jun 21 20:03:39 assbox systemd[1]: Using hardware watchdog 'iTCO_wdt', version 4, device /dev/watchdog0
Jun 21 20:03:39 assbox systemd[1]: Watchdog running with a hardware timeout of 10min.
Jun 21 20:03:39 assbox kernel: watchdog: watchdog0: watchdog did not stop!
Jun 21 20:03:39 assbox systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 4, device /dev/watchdog0
Jun 21 20:03:39 assbox systemd-shutdown[1]: Watchdog running with a hardware timeout of 10min.
Jun 21 20:03:39 assbox systemd-shutdown[1]: Syncing filesystems and block devices.
Jun 21 20:03:39 assbox systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jun 21 20:03:39 assbox systemd-journald[309]: Received SIGTERM from PID 1 (systemd-shutdow).
Jun 21 20:03:39 assbox systemd-journald[309]: Journal stopped

Clean

Jun 21 20:58:15 assbox systemd[1]: Reached target System Shutdown.
Jun 21 20:58:15 assbox systemd[1]: Reached target Late Shutdown Services.
Jun 21 20:58:15 assbox systemd[1]: systemd-reboot.service: Deactivated successfully.
Jun 21 20:58:15 assbox systemd[1]: Finished System Reboot.
Jun 21 20:58:15 assbox systemd[1]: Reached target System Reboot.
Jun 21 20:58:15 assbox systemd[1]: Shutting down.
Jun 21 20:58:15 assbox systemd[1]: Using hardware watchdog 'iTCO_wdt', version 4, device /dev/watchdog0
Jun 21 20:58:15 assbox systemd[1]: Watchdog running with a hardware timeout of 10min.
Jun 21 20:58:15 assbox kernel: watchdog: watchdog0: watchdog did not stop!
Jun 21 20:58:15 assbox systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 4, device /dev/watchdog0
Jun 21 20:58:15 assbox systemd-shutdown[1]: Watchdog running with a hardware timeout of 10min.
Jun 21 20:58:15 assbox systemd-shutdown[1]: Syncing filesystems and block devices.
Jun 21 20:58:15 assbox systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jun 21 20:58:15 assbox systemd-journald[305]: Received SIGTERM from PID 1 (systemd-shutdow).
Jun 21 20:58:15 assbox systemd-journald[305]: Journal stopped

Last edited by Derp (2024-06-21 20:34:17)

Elyrial

Member

Registered: 2024-06-21

Posts: 3

Re: [SOLVED] SDDM crashing on shutdown/reboot

This looks like a SDDM issue to me, and since both of you are using KDE Plasma which likely has X11 by default, wayland might (maybe) cause some problems. I remember having KDE Plasma last year and there were a lot of bugs in my sessions. Consider switching to X11 temporarily to see if the problem still exists, or maybe another Display Manager (LightDM, GDM)

Last edited by Elyrial (2024-06-21 21:38:22)

Derp

Member

Registered: 2024-06-21

Posts: 2

Re: [SOLVED] SDDM crashing on shutdown/reboot

I'm not so sure since SDDM exit completely before the freeze occur. And yes, SDDM with X11 generate a bunch of errors and has tons of bugs. But i have a hard time grasping how that could impact the system when systemd have completely shut them down.

Dirty (restarted by signing out to SDDM and hitting the reboot button)
journalctl -b -2 | grep "sddm"

Jun 21 20:03:34 assbox sddm[612]: Message received from greeter: Reboot
Jun 21 20:03:34 assbox sddm-helper-start-x11user[264437]: Signal received: SIGTERM
Jun 21 20:03:34 assbox sddm-helper-start-x11user[264437]: quitting helper-start-x11
Jun 21 20:03:34 assbox sddm-helper-start-x11user[264437]: Stopping server...
Jun 21 20:03:34 assbox sddm-helper[264436]: Signal received: SIGTERM
Jun 21 20:03:34 assbox systemd[1]: Stopping Session c4 of User sddm...
Jun 21 20:03:34 assbox sddm[612]: Error from greeter session: "Process crashed"
Jun 21 20:03:34 assbox sddm[612]: Auth: sddm-helper (--socket /tmp/sddm-auth-0e42c0e6-990c-49ce-b5aa-c8922b196e31 --id 8 --start /usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--BTKfNP --user sddm --display-server /usr/bin/X -nolisten tcp -background none -seat seat0 -noreset -keeptty -novtswitch -verbose 3 --greeter) crashed (exit code 1)
Jun 21 20:03:34 assbox sddm[612]: Error from greeter session: "Process crashed"
Jun 21 20:03:34 assbox sddm[612]: Auth: sddm-helper exited with 1
Jun 21 20:03:34 assbox sddm[612]: Greeter stopped. SDDM::Auth::HELPER_AUTH_ERROR
Jun 21 20:03:34 assbox sddm[612]: Signal received: SIGTERM
Jun 21 20:03:34 assbox sddm[612]: Socket server stopping...
Jun 21 20:03:34 assbox sddm[612]: Socket server stopped.
Jun 21 20:03:34 assbox systemd[1]: sddm.service: Deactivated successfully.
Jun 21 20:03:34 assbox systemd[1]: Stopped Session c4 of User sddm.
Jun 21 20:03:34 assbox (sd-pam)[264422]: pam_unix(systemd-user:session): session closed for user sddm

Clean (restarted using the reboot button in KDE)
journalctl -b -1 | grep "sddm"

Jun 21 20:58:14 assbox sddm-helper[716]: Signal received: SIGTERM
Jun 21 20:58:14 assbox sddm[647]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Jun 21 20:58:14 assbox sddm[647]: Auth: sddm-helper (--socket /tmp/sddm-auth-ae36ccb2-0712-4031-a0ec-63cc08294063 --id 3 --start /usr/bin/startplasma-x11 --user dodde --display-server /usr/bin/X -nolisten tcp -background none -seat seat0 -noreset -keeptty -novtswitch -verbose 3) crashed (exit code 1)
Jun 21 20:58:14 assbox sddm[647]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Jun 21 20:58:14 assbox sddm[647]: Auth: sddm-helper exited with 1
Jun 21 20:58:14 assbox sddm[647]: Signal received: SIGTERM
Jun 21 20:58:14 assbox sddm[647]: Socket server stopping...
Jun 21 20:58:14 assbox sddm[647]: Socket server stopped.
Jun 21 20:58:14 assbox systemd[1]: sddm.service: Deactivated successfully.

Last edited by Derp (2024-06-21 22:09:15)

tsuritsuritsuri

Member

Registered: 2024-06-14

Posts: 2

Re: [SOLVED] SDDM crashing on shutdown/reboot

Okay, I'm back. What I found was that the problem might be GPU related. The common factor that I noticed was hybrid GPU (i.e., ryzen/nvidia or intel/nvidia). I was using nvidia-dkms package before, so I switched to the proprietary NVIDIA ones. Still facing the same issue, now even while I was using the laptop (which wasn't happening before). Switched to nvidia-open-dkms drivers and now it has been running without issues for about 2 days. I can't say for sure this will be the case forever but at least for now it's the only thing that has shown good results. I thought it was Arch related but nope, other distros also encounter the same issue according to some quick searches. Not sure why this happens but it apparently has been going for a while now. I might be completely mistaken but hey, who knows. Give it a try and maybe you can fix it for now.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,117

Re: [SOLVED] SDDM crashing on shutdown/reboot

There are some known bugs with the proprietary nvidia driver in version 550 corrupting kernel memory, most problematically potentially leading to crashes during updates, or the sddm reboot failure you're seeing. The nvidia-open packages are known to avoid this, as is e.g. downgrading to 535 via the corresponding AUR package. Hopefully the next stable series 560 is going to fix this (... afaik there's been talks of reccommending nvidia-open with that version for capable GPUs anyway) see also this thread: https://bbs.archlinux.org/viewtopic.php?id=293400