https://bugs.kde.org/show_bug.cgi?id=374538
--- Comment #63 from [email protected] --- (In reply to Nate Graham from comment #62) > If you're not using Systemd, then your problem has completely different root > causes and potential resolutions compared the bug described here, and should > be discussed elsewhere. It's also probably not a KDE bug, as both SysVinit > and Systemd are are far below any KDE code. > > > Both options seem somewhat anachronistic in 2022. > Indeed, which is why one of the reasons SystemD was invented was to fix this > problem. :) It allows deterministic ordering of startup and shutdown process > and fine-grained control over how long a stuck process can halt shutdown. > The distro just has to set that up properly. One reason why I finally said "Good riddance!" to systemd was that enervating "A stop job is running...". At one point I was sufficiently fed up with that. I switched to System V and never looked back. > > So this is a solved problem in 2022 if you're using modern software that's > configured well. This seems to imply that one now has to choose between Plasma + "modern" systemd (suggesting that "modern == good") or having to accept certain problems. This is new to me, since AFAIK, KDE once pledged that Plasma would continue to work with System V. If this is not the case anymore, KDE should state it clearly, so that people know and can adapt their choices accordingly. > > I would recommend that you discuss the "Ding" problem with your distro. "Inside-out" thinking instead of "outside-in" may ease problems in the short run but in the long run is a proven recipe for disaster. -- You are receiving this mail because: You are watching all bug changes.
