[Pkg-utopia-maintainers] Bug#668251: org.freedesktop.ConsoleKit.Manager.Stop not working

[Simon McVittie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

reassign 668251 consolekit
thanks

I don't think this is D-Bus' fault: the message is being delivered,
but ConsoleKit is returning an error rather than doing what you ask.

On 10/04/12 20:04, Harald Dunkel wrote:
> AFAIR the users in group "powerdev" are allowed to shut down.

Not via ConsoleKit, at least in the version in unstable. I think HAL
allowed members of powerdev to manipulate power states (but only by
sending D-Bus messages to HAL, not by sending D-Bus messages to
ConsoleKit).

If ConsoleKit is working correctly, you shouldn't need to be in a long
list of groups on a current testing/unstable system: the idea of
ConsoleKit/PolicyKit is that the policy most people want is something
like "whoever has the active local login session can control the
hardware", and installations where that isn't true can reconfigure the
policy. I agree they're under-documented, though.

Specifically, you should no longer need plugdev, powerdev, netdev.

>> That should mean that you can Stop the system if your session is
>>  considered active, but if another user is logged-in in parallel,
>>  you have to authenticate first.
> 
> There is nobody logged in but me. I wasn't asked for authentication
> except at login time, either.

OK, so this means CK doesn't think you have an active session...

>> If you run ck-list-sessions, does it say your session is active?
> 
> ck-list-sessions just exits with 0. No screen output.

... and this means CK doesn't think there are any sessions, active or
not. Being logged in once should look more like this:

reptile% ck-list-sessions
Session7:
	unix-user = '1000'
	realname = 'Simon McVittie'
	seat = 'Seat1'
	session-type = 'x11'
	active = TRUE
	x11-display = ':0'
	x11-display-device = '/dev/tty9'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2012-04-10T18:52:44.807283Z'
	login-session-id = '4294967295'

Do you have libpam-ck-connector installed?

When you say "sitting on the console" do you mean you logged in to a
text virtual console (login(1) or whatever), or do you mean you logged
in to an X display manager like xdm, gdm, kdm etc.? If you logged in
to an X display manager, which one?

> What exactly do you mean by "session"? Sorry for asking, but the 
> consolekit package does not provide proper documentation. Esp. 
> ck-list-sessions does not provide a man page :-(.
> 
> I have the impression that this is some kind of mandatory scheme to
> make consolekit working, so how comes that I could login on the 
> console without it?

As far as I understand it, CK's purpose is to to keep track of who is
logged in, and the properties of those login sessions, so that we can
have policies like:

    if more than one user is logged-in locally, only an administrator
    can shut down the computer

    if only one user is logged-in locally then they can shut down the
    computer

(for which you have to be able to define "logged-in" and "local").

Loosely, if you log in on a text console that's a session, and if you
log in to gdm/xdm/kdm/whatever that's also a session.

    S
-----BEGIN PGP SIGNATURE-----

iQIVAwUBT4SVsk3o/ypjx8yQAQjgRQ//aQ/vHq4705WoktaJYBtYo7qI2J/kh2lH
2ones/OGHmV7O4d4C4WEICnzmmoa4RTfxFZlBG3HgHl4nt36ud9FDWLkNf8AdsDO
iQ2zzGiWNMaAeQpbcTWMsymPwqFS77mTBTlnXYYcqS2K8sFbT5nDnxDyGejaa+D2
ekavQwwvF2w9392tsFGwHV6CP1qEE62NPk1ADp870gYbMBoqp0iyt2+cOjglRE0H
69wgQfOJzGo8R5QIjzOAI3lU7jxSXBKwKistM8s8Rkh0vTqZhVdds6OsZodj0F63
ZE3Cuv2fRy7EfiWVDdTDc75sa+ZthRYDYENz1ORedFdMYb1rmsL7+QSbmMS70aTv
BK/B0JZVsGAh8pvJh/dyAQS4H5aGPFOlZJ08vG5TrPA5LIJY5KjqZ2yVmgnnwUSh
SSuovkT/aEUje7fHkCzWradbdgBglc4vVvxCggfZ58CPt8EauQdqjIZMe5DWQkC8
Vx9TcFnqklH6QooPnrXHkEwIUkxI4yp6a7fb/vF5YERhAMa+i7tOrUAQe3fSHtnA
KEpabNZAzWru+WEtKhSn+Hr/MvywhiblITps9jgr7ZyLlI2YFcOkfGmzzf5gU0HW
HL8eE9rCDrB//pXVDaFbaXWWFnyvHfp2oYvZkkhEjy8JrPoiIhAurqp31fzotXWs
qSPINW/PRJo=
=lKAQ
-----END PGP SIGNATURE-----