But note that when invoking org.freedesktop.login1.Manager->CanPowerOff() from a remote session, its output is:
"challenge"
instead of "yes" that an active (local) session produces.
That means that when indicator-session calls org.freedesktop.login1.Manager->PowerOff() with a "false" parameter to prevent prompting, then PowerOff() does nothing.
So, indicator-session should either
1) Hide the actions that return "challenge", or
2) Enable the prompt when the action specified "challenge".
(2) would allow remote users to shutdown the server, so I think everyone in this bug report prefer (1). :)
In Trusty, the relevant code has been rewritten to use logind instead of consolekit: bazaar. launchpad. net/~indicator- applet- developers/ indicator- session/ trunk.14. 04/revision/ 388
http://
But note that when invoking org.freedesktop .login1. Manager- >CanPowerOff( ) from a remote session, its output is:
"challenge"
instead of "yes" that an active (local) session produces.
That means that when indicator-session calls org.freedesktop .login1. Manager- >PowerOff( ) with a "false" parameter to prevent prompting, then PowerOff() does nothing.
So, indicator-session should either
1) Hide the actions that return "challenge", or
2) Enable the prompt when the action specified "challenge".
(2) would allow remote users to shutdown the server, so I think everyone in this bug report prefer (1). :)