restart impossible when a remote ssh session is running

Bug #1082211 reported by Emmanuel Thomé
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
consolekit (Ubuntu)
Confirmed
Low
Unassigned
lightdm (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

(assigning to lightdm, although it's broader than that. Not clear which component is to blame exactly).

Let X be a laptop running ubuntu 12.10. It's an x86-64 cpu for that matter, but no one cares.

Assume an ssh server is running on X, and someone is logged in via ssh from another machine Y to machine X.

Now if X is showing a lightdm login screen, there is no way the ``restart'' button (from the top-right menu) can work. It is simply ignored. There is no message either.

If some user is logged on X, and he opens up the top-right menu and goes to ``restart'', one of two things may happen.
  - If the remote session is under this very user, then the session is killed, and the computer restarts.
  - If the remote session is under another user (root, for the situation I tried), then the user's session is nuked, but the computer does not restart, and returns back to the lightdm login screen.

I find this quite irritating. Ssh sessions to my laptop may happen. When I have physical access to it, I would like to be able to restart/shut down the machine without having to either do a dirty shutdown (5s press) or hunt manually for ssh session and kill -9 them, or ctrl-alt-f1, root login, and reboot.

I would conceive it if someone considers it's ''dangerous'' to kill incoming ssh sessions. Not that I share this opinion, but I imagine it may exist. If so, would it be possible, please, to have a dialog box like ``yes, I mean it'' if the system decides it's perhaps unwise to proceed to reboot ?

Best,

E.

Revision history for this message
Richard Hansen (rhansen) wrote :

Added consolekit to the affected packages because I believe this is the package responsible (maybe with policykit?) for denying shut down or restart based on who's logged in.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in consolekit (Ubuntu):
status: New → Confirmed
Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, that's known as bug #861171

Changed in consolekit (Ubuntu):
importance: Undecided → Low
Changed in lightdm (Ubuntu):
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.