https://bugs.kde.org/show_bug.cgi?id=516129
Tobias Fella <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-login-manager/-/c |ma/plasma-login-manager/-/c |ommit/4a57d986fb6afe5e3755e |ommit/6f2295cc6e9d667447a3d |8579d69cfb91417e1aa |ae02f48ccd704998c19 --- Comment #2 from Tobias Fella <[email protected]> --- Git commit 6f2295cc6e9d667447a3dae02f48ccd704998c19 by Tobias Fella, on behalf of Oleg Tsvetkov. Committed on 08/06/2026 at 13:23. Pushed by tfella into branch 'Plasma/6.7'. startkde: Treat KWin exit code 15 as a clean shutdown When login finishes, plasma-login-wayland.target is stopped and the greeter's kwin_wayland is sent SIGTERM. KWin watches SIGTERM through KSignalHandler and connects signalReceived straight to QCoreApplication::exit (src/main_wayland.cpp), so it exits with the signal number, that is exit code 15. systemd treats termination by SIGTERM as clean by default, but not a plain exit code of 15, so the unit is marked failed on every login even though login succeeded and the session compositor has already taken over: plasma-login-kwin_wayland.service: Main process exited, code=exited, status=15/n/a plasma-login-kwin_wayland.service: Failed with result 'exit-code'. For this unit 15 only comes from SIGTERM: startup and CLI errors exit 1, crashes are reported as a signal, and the path that forwards a wrapped process's exit code is not used here. Add SuccessExitStatus=15 so the expected teardown is no longer reported as a failure. (cherry picked from commit 4a57d986fb6afe5e3755e8579d69cfb91417e1aa) M +1 -0 src/frontend/startkde/plasma-login-kwin_wayland.service.in https://invent.kde.org/plasma/plasma-login-manager/-/commit/6f2295cc6e9d667447a3dae02f48ccd704998c19 -- You are receiving this mail because: You are watching all bug changes.
