Bug 271538 - shutdown dialog should check for other users before the countdown
Summary: shutdown dialog should check for other users before the countdown
Status: RESOLVED DUPLICATE of bug 183274
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.6
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-23 09:44 UTC by Rufus Dee
Modified: 2011-04-29 19:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rufus Dee 2011-04-23 09:44:49 UTC
Version:           4.6 (using KDE 4.6.2) 
OS:                Linux

When invoking KDESC's shutdown dialog, it starts its 30 second timeout before executing the default action (in my case the default is to shut down). Only after the timeout is through, the shutdown dialog checks if there's other people logged in (on virtual TTYs or other X sessions). This may lead to the (nowadays, often fanless, thus inaudible) computer running all night.
The convenience of being able to shut down the computer via the power button is severely deminished if I have to reach for the mouse/keyboard to skip the count down before I can walk away from the computer.

Reproducible: Always

Steps to Reproduce:
1. log in some user to the SC
2. Log in some user to TTY1 (TTYs 2 to 6 or another X session work as well)
3. Ctrl-Alt-F7 back to the SC
4. Press Ctrl-Alt-Del (using the power button or kickoff works as well)
5. See no obvious problems, walk away, return the other morning

Actual Results:  
The user (1) is logged out of the SC, but instead of shutting down the computer asks what to do with the user (2) logged in to another session

Expected Results:  
5. The shutdown dialog realizes its default is set to Shutdown, checks for other open sessions, and displays a warning somewhere
Comment 1 Christoph Feck 2011-04-29 19:32:35 UTC
*** This bug has been marked as a duplicate of bug 183274 ***