https://bugs.kde.org/show_bug.cgi?id=360673
--- Comment #3 from Thomas Lübking <[email protected]> --- That link seems about the epic "systemd broke nohup" concept. Status quo (ante) is that everything in the shell should receive a SIGHUP by the shells termination and quit in return. This somehow seems to fail. Then there'd be explicit SIGTERMs by new and objected logind behavior and only if that fails and as very last resort there should be (after a while) a SIGKILL. If we fail on the SIGHUP, we'll likely fail the SIGTERM as well (same code path via QApplication::exit()) ie. there'd not even be a change by the new logind behavior and ultimately kwin_x11 would get nuked by the SIGKILL (which is not ignorable), but SIGKILL is a failsafe resort and no way a clean way to quit a process (thus the timeouts) tl;dr - kwin should quit on SIGHUP, then forget about the rest of what I said (new loginctl is doing wrong in trying to fix broken clients. We're supposed to exit reliably on sighup. If we're broken, just fix us and do not rely on quirks of the session system) -- You are receiving this mail because: You are watching all bug changes.
