Still experiencing this with Lucid daily live (built on 2010.02.13) - fully patched as of 2010.02.19, with the following caveats...
1) An active VTY session using the same account as used for the GDM login will *not* stop shutdown. The VTY is simply crushed during shutdown. 2) An active VTY session with a different active login (e.g. an "sudo su") will prompt for credentials, but results in the behavior described in the original post (i.e. X session is killed). 3) A terminal window via Gnome (even a terminal window with an active "sudo su" login) will *not* stop shutdown. While I am ambivalent as to the correct handling of extra logins via Gnome (e.g. terminal "sudo su") I feel pretty strongly about VTY logins. Any VTY login, either same user or different user (e.g. via "sudo su"), should prompt the Gnome user requesting the shutdown for authorization to proceed. A user sophisticated enough to initiate a VTY login can cleanly take care of the issue when notified of multiple logins on shutdown. I think there is a case to be made for consistent action with Gnome terminal logins as well (specifically terminals logged in as an alternate user) but I *do* want my desktop to shutdown when requested, without jumping through hoops. Opinions on this will vary I'm sure. I have not tested this via telnet, ssh, etc - only from the VTYs *However*, the killing of the X session on cancel remains a serious problem in any scenario. -- Consolekit / Policykit interaction with indicator-applet-session produces unexpected results https://bugs.launchpad.net/bugs/459705 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
