[Maverick] Cannot shutdown when multiple users are logged in

[Speedy Gonzalez]

Binary package hint: gnome-panel

Hi,

I use maverick.

When more than one user is logged in, shutdown (clicking on "shut down” in the session applet) seems not work correctly. Instead of shutting down the system (and ask for root password, because more than one user is currently logged in), the active user is logging out.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-panel 1:2.30.2-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Wed Oct 13 20:43:02 2010
GConfNonDefault:
 /apps/panel/general/applet_id_list=[fast_user_switch_screen0,trashapplet_screen0,workspace_switcher_screen0,window_list_screen0,show_desktop_button_screen0,indicator_applet_screen0,notification_area_screen0,clock_screen0]
 /apps/panel/general/object_id_list=[browser_launcher_screen0,menu_bar_screen0,object_0]
 /apps/panel/general/toplevel_id_list=[bottom_panel_screen0,top_panel_screen0]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 LANGUAGE=de:en
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: gnome-panel

[Pedro Villavicencio (pedro)]

that's reproducible with every single user created on your machine? could you attach your ~/.xsession-errors file to the report? thanks.

[Speedy Gonzalez (tomislav159)]

Yes this is reproducible with every single user. I have tested 3 users.

[Speedy Gonzalez (tomislav159)]

Also found this .xsession-errors.old

[Aurélien COUDERC (coucouf)]

I can confirm this bug after upgrading from lucid to maverick.
Users with administrative rights used to be asked for their password when shutting down the system and other users were logged in. This doesn't work anymore.

Please note the following line in the .xsession-errors.old attached above:
gnome-session[1745]: WARNING: Unable to stop system: Authorization is required

[Aurélien COUDERC (coucouf)]

Strangely enough, the DBUS call to console kit fails in gsm_consolekit_attempt_stop in gsm-consolekit.c :
         res = dbus_g_proxy_call_with_timeout (manager->priv->ck_proxy,
                                              "Stop",
                                              INT_MAX,
                                              &error,
                                              G_TYPE_INVALID,
                                              G_TYPE_INVALID);

whereas the same call from a shell works :
dbus-send --system --dest=org.freedesktop.ConsoleKit --type=method_call --print-reply --reply-timeout=4294967295 /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop

May the policykit authentication agent have been already killed when the gnome-session DBUS call is issued ?

[Jamie Strandboge (jdstrand)]

This also affects Natty.

[Jamie Strandboge (jdstrand)]

I think Aurélien's observation may be correct because I was trying to figure out how to get the pk auth dialog to pop up in the gdm session (ie, the login window). On natty at least, this was not working because the polkit-gnome-authentication-agent-1 is not starting. I found that if I did:
$ sudo ln -s /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop /usr/share/gdm/autostart/LoginWindow/

then logged in as two different users and tried to restart via the login window restart action, then I would get the policykit dialog to pop up. Note this will not fix the bug when in a user's session; I am just passing the information along).