[Pkg-utopia-maintainers] Bug#652374: consolekit: fails to activate dbus service consolekit on first login attempt
Martin Steigerwald
Martin at Lichtvoll.de
Fri Dec 16 20:29:16 UTC 2011
Package: consolekit
Version: 0.4.5-1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading my Wheezy to the Debian repository contents of today +
installing kernel 3.2-rc4 (to get faster hibernation by new
multi-threaded image writing).
* What exactly did you do (or not do) that was effective (or
ineffective)?
I logged into KDE 4.6.5 session via KDM.
* What was the outcome of this action?
>From daemon.log:
Dec 16 21:11:17 localhost dbus[1285]: [system] Activating service name='org.freedesktop.RealtimeKit1' (using serv
icehelper)
Dec 16 21:11:17 localhost dbus[1285]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Dec 16 21:11:17 localhost rtkit-daemon[1924]: Successfully called chroot.
Dec 16 21:11:17 localhost rtkit-daemon[1924]: Successfully dropped privileges.
Dec 16 21:11:17 localhost rtkit-daemon[1924]: Successfully limited resources.
Dec 16 21:11:17 localhost rtkit-daemon[1924]: Running.
Dec 16 21:11:17 localhost rtkit-daemon[1924]: Watchdog thread running.
Dec 16 21:11:17 localhost rtkit-daemon[1924]: Canary thread running.
Dec 16 21:11:17 localhost dbus[1285]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servic
ehelper)
Dec 16 21:11:19 localhost ntpdate[1563]: adjust time server 160.45.10.8 offset 0.376389 sec
Dec 16 21:11:32 localhost dbus[1285]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
Dec 16 21:11:42 localhost dbus[1285]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
Dec 16 21:11:42 localhost kdm: :0[1495]: Cannot open ConsoleKit session: Unable to open session: Activation of org.freedesktop.ConsoleKit timed out
Dec 16 21:12:19 localhost kdm: :0[1495]: Cannot read from greeter for display :0
After that for example KDE 4.6.5 power management was not able to hibernate
the laptop. The power management locked the screen, but did not initiate
the hibernation, although calling pm-hibernate from command line did the trick.
* What outcome did you expect instead?
Absence of the error message and working powermanagement.
Since seems like debian bug #562026:
kdm cannot open ConsoleKit session on first login attempt
http://bugs.debian.org/562026
but I have a consolekit version past 0.4.1-3 in which Ingo Kasten found the
bug fixed.
This happens on a ThinkPad T42. On a ThinkPad T520 with Debian Sid and same
consolekit version and 3.2-rc4 amd64 kernel I did't see this issue. Maybe
a race condition? My ThinkPad T23 is still updating (slow BTRFS), when it
happens there, too, I will report back.
Thanks,
Martin
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (450, 'testing'), (400, 'unstable'), (110, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-rc4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages consolekit depends on:
ii dbus 1.5.8-1
ii libc6 2.13-21
ii libck-connector0 0.4.5-1
ii libdbus-1-3 1.4.16-1
ii libdbus-glib-1-2 0.98-1
ii libglib2.0-0 2.30.2-4
ii libpolkit-gobject-1-0 0.102-2
ii libx11-6 2:1.4.4-4
ii zlib1g 1:1.2.3.4.dfsg-3
Versions of packages consolekit recommends:
ii libpam-ck-connector 0.4.5-1
consolekit suggests no packages.
-- no debconf information
More information about the Pkg-utopia-maintainers
mailing list