Comment 19 for bug 315865

(In reply to comment #9)
> > You mean something like yum / apt-get update glibc* xorg* kde* (etc) :)
>
> Not relevant:
> - if the extra confirmation dialog is already shown when I press shutdown. I'm
> still behind my computer for 1-2 seconds. It's a good final reminder of "oh oh
> ... what did I leave running in tty1?".
> - your use case requires an experienced computer user who knows a lot more then
> the general home user.
> - if yum or apt-get can't handle a Ctrl+C or other SIGTERM, there is a bigger
> issue. The shutdown dialog doesn't need to have a workarond for this.

Its very relevant We're not talking about a workaround for apt-get or yum. The point I was making was that the default behaviour of kdm on shutdown / reboot was to go ahead and do it after a few seconds regardless of what was running in the background (as per comment 7). As you point out the average home user is not as savy as an "experienced user" and does not know or understand that hitting a runlevel 0 or 6 condition and having yum or apt-get halt an update in the middle of lets say updating Xorg could very easily leave XWindows in a state where it will not run or worse, in the case of glibc have the computer not be able to come up at all. And even the inexperienced user updates his or her computer. So having the computer shutdown or reboot without explicitly issuing the command to shutdown open consoles should be a big no no and should not be the default behavior. Especially since KDE has added this really great feature to KDM.

The problem is that is being discussed pertains primarily for "experienced users" that have shutdown all consoles but is warned that a tty session is open even though all of them are closed. The feature requested is that there be a check box or some other mechanism to allow a user to "knowingly" switch off the warning permanently and go ahead and reboot without asking the next time. And just as important, to be able to switch it back on once the bug in upstart is fixed.

Now if you're suggesting that the warning have an option to have it go ahead and shutdown after a certain time period then as an option. I agree this would be a great option. But again, it should not be default. It should be explicitly switched on.

Even though the problem results from a bug in other software, it still doesn't make it any less annoying. If the user changes the default "warning" behavior then its the users problem. If KDE is capable of warning the user that there are consoles open then, it should and it should prevent the shutdown or reboot unless explicitly instructed to do so. If consoles are open then the user should be reminded of it just in case something important is running in them. And by the way even the experienced user gets tired or overwhelmed by whats going on around him. The feature itself is highly welcomed and great addition to KDM.

> I hope this feature can be implemented as soon as possible. I make jokes like
> "haha the computer is still on with a 'can't shutdown XYZ' message" about
> Windows. Well can't do that anymore. ;)