Bug 345577 – Consolekit: Can't shutdown from logout window in gnome menù

• Status: RESOLVED NEEDINFO
• Product: Gentoo Linux

[Description jeff 2010-11-15 08:01:16 UTC]

I can't shutdown from logout window in gnome menù.
I think that is something related to the latest consolekit version.

Reproducible: Always

[Comment 1 Rafał Mużyło 2010-11-15 13:21:31 UTC]

Is this the problem covered by postinst warning ?

[Comment 2 Samuli Suominen (RETIRED) 2010-12-06 09:55:45 UTC]

Provide:

- Information how you start X and content of possible ~/.xinitrc or ~/.xsession files from your home directory.

- `ck-list-sessions` output before starting X server (if you log into console before, and use startx or similar) and then same after you've logged in.

- emerge --info

- Information if /etc/init.d/consolekit is running or not. 

- emerge -pv dbus consolekit pambase output

Then reopen and we'll see...

[Comment 3 Peter Waller 2011-12-19 12:59:13 UTC]

Created attachment 296355 [details]
emerge --info

[Comment 4 Peter Waller 2011-12-19 12:59:34 UTC]

Created attachment 296357 [details]
ck-list-sessions before starting xdm

[Comment 5 Peter Waller 2011-12-19 13:01:38 UTC]

Created attachment 296359 [details]
ck-list-sessions after (not working)

Problem is intermittent. This is the output of ck-list-sessions when it is working, and the shutdown button is present.

[Comment 6 Peter Waller 2011-12-19 13:01:50 UTC]

Created attachment 296361 [details]
ck-list-sessions after (working)

[Comment 7 Peter Waller 2011-12-19 13:04:46 UTC]

Please re-open the bug. I am not the original submitter, but I am affected by the problem.

Output of emerge -pv dbus consolekit pambase

[ebuild   R    ] sys-apps/dbus-1.4.16  USE="X -debug -doc (-selinux) -static-libs -test" 1,846 kB
[ebuild   R    ] sys-auth/consolekit-0.4.5-r1  USE="pam policykit -debug -doc -test" 416 kB
[ebuild   R    ] sys-auth/pambase-20101024  USE="consolekit cracklib sha512 -debug -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -passwdqc (-selinux)" 4 kB

It appears that there is some sort of problem with consolekit, "/etc/init.d/consolekit status" reports that it is stopped, but "/etc/init.d/consolekit start" states that it is already running and restart fails for the same reason.

Apologies for attachment spam. In hindsight I probably only needed to attach the emerge.info.

[Comment 8 Samuli Suominen (RETIRED) 2012-01-23 15:20:46 UTC]

(In reply to comment #7)
> Please re-open the bug. I am not the original submitter, but I am affected by
> the problem.
> It appears that there is some sort of problem with consolekit,
> "/etc/init.d/consolekit status" reports that it is stopped, but
> "/etc/init.d/consolekit start" states that it is already running and restart
> fails for the same reason.

This would happen if dbus and consolekit are missing from the "default" boot level. 
And as a result, they get started by something else than the init script.

I don't see anything here that would warrant a reopening though, it's most likely a local setup problem since XDM doesn't have internal consolekit support but relies on users hacking the /etc/X11/Sessions/ files for ck-launch-session. One dbus-launch or ck-launch-session in wrong place and it shows as proper in ck-list-sessions, but actually doesn't work. Bug 360987.

Use something sane, like lightdm or gdm