[Solved] consolekit and polkit under systemd

Question

I was wondering if I still had vestiges of the sysv init left on my system since I have supposedly gone completely over to systemd.
The consolekit wiki page strongly suggests that systemd is incompatible with it. If I do "systemctl list-unit-files --no-pager|grep -i console" I see
console-kit-daemon.service disabled
console-kit-log-system-restart.service static
console-kit-log-system-start.service static
console-kit-log-system-stop.service static
console-shell.service disabled
Yet when I do "systemctl --all --no-pager|grep -i console" for some reason I see
console-kit-daemon.service loaded active running Console Manager
console-...m-start.service loaded active exited Console System Startup Logg
It strikes me as strange for a loaded, active, running service to be disabled. Anyway should consolekit be "uninstalled" and completely eliminated?
Polkit causes somewhat similar questions although it is less obvious from the wiki that it is incompatible with systemd.
Journalctl does show systemd starting up polkit and consolekit, but it also shows several messages, "console-kit-daemon[553]: missing action", and for polkitd it shows both a "Registered Authentication Agent" and later a "Unregistered Authentication Agent" - for several different buses, apparently. Not sure if that is normal.
Just wondering how all this fits together, and if some of it should be gone now that systemd is here.
Last edited by PaulBx1 (2013-01-21 19:35:10)

Answer 1

I wonder if there are any more things like that? I was a little surprised there were no warnings on the systemd conversion to get rid of consolekit, or that the compatibility package didn't take care of it. Maybe there were warnings and I just missed them.
I also wonder about the "ck-launch-session" at the end of my .xinitrc file. The consolekit wiki article says,
An easy method to be able to remove ConsoleKit is to automatically log in to a virtual console and start X from there. It is important that, as mentioned in the latter article, the X server is started on the same virtual console that you log in to, otherwise logind can not keep track of the user session. You can then simply remove ck-launch-session from your ~/.xinitrc.
I don't quite understand that. Just delete the line? Or does something else (having to do with systemd) go in there? And why the virtual console bit? Why not just go to single user and handle it there?
Here is my .xinitrc:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
exec ck-launch-session startlxde
Last edited by PaulBx1 (2013-01-21 07:10:23)