https://bugs.kde.org/show_bug.cgi?id=436928
--- Comment #2 from Harald Sitter <sit...@kde.org> --- (In reply to Nate Graham from comment #1) > You're talking about in the Discover UI itself, right? Yes, well, the KCM I suppose. Depending on a specific user's way of using the system it may be more appropriate to set the offline update behavior to reboot (after update the system reboots) or power-off (after update the system powers off). e.g. consider two office use cases: User A has a system with SSD and tends to grab a cup of coffee after entering the office and turning on the PC. reboot is a reasonable system for this scenario because the user will be away from the machine for a while anyway. Meanwhile we start into the update target, apply the update, reboot. By the time the user is back we'd ideally be done and they can log in. User B has a system with a HDD and doesn't drink coffee. power-off may be a more reasonable approach. They will power off the system when they leave the office anyway. We can simply set the offline trigger to power-off and instruct ksmserver/the greeter to perform a reboot instead of a power-off. The user leaves the office. The PC reboots into the update target, applies the update, powers off. -- You are receiving this mail because: You are watching all bug changes.
