https://bugs.kde.org/show_bug.cgi?id=336369
--- Comment #19 from Martin Flöser <mgraess...@kde.org> --- (In reply to Nate Graham from comment #18) > The more I think about it, the more I find myself agreeing that we should > *at least* have the suspend option available. That's a non-destructive > action for all use cases, and will make quite a few people happy given the > use cases we've had presented so far. That is not true. A long running job might get cancelled due to suspend. My example for this is a long calculation in a science department. If we allow suspend a competing researcher might be able to destroy the work of a researcher. If we offer this it must be configurable. > > Other familiar platforms (macOS, Windows, GNOME) also go so far as to allow > you to shut down and reboot from the lock screen, even in a multi-user > environment. They first display a scary warning declaring "This action may > cause you or other logged-in users to lose work. Are you sure you want to > proceed?" > > We might consider doing something similar, if we warn the user about the > potential consequences and only allow it for admin accounts when other users > are logged in. We cannot. If an application asks to save a document the shutdown is stuck. The screen is locked and it is not possible to interact with the application requiring interaction. That's how session shutdown is guaranteed to work on Linux. -- You are receiving this mail because: You are watching all bug changes.
