I'm using SLIM and Openbox and am in the process of converting to systemd.
I've added the needed configuration files for systemd.
I can boot using the wiki instructions here https://wiki.archlinux.org/index.php/Sy … stallation
I've added SLIM as a service using https://wiki.archlinux.org/index.php/Sy … er_systemd
My question is: Do I still need ConsoleKit? So far this seems to be working for me but I'm not sure if I need to add ConsoleKit somehow.
BTW: I start Openbox with the usual
exec ck-launch-session openbox-session
when using initscripts.
Last edited by bergersau (2012-10-11 05:31:52)
If you are using slim, you should not be using ck-launch-session anyway. It clearly states this in the wiki (kind of all over the place). If you continue to use slim, you have no choice but to keep consolekit, as it is still a dependency. Eventually systemd will be able to autheticate sessions with polkit. But this version has been in testing since mid september.
Thanks WonderWoofy, I just double checked my ~/.xinitrc and found I had commented out ck-launch-session when I installed SLIM many moons ago - Sorry My Bad, I was working from my 'obviously flawed' memory.
As ConsoleKit is a dependency of SLIM I'll obviously need to keep it around for the time being. One final question - Do I need to do anything more with it than just have it installed on the system?
No, slim takes care of that on its own (also stated in the wiki).
Edit: https://wiki.archlinux.org/index.php/Slim#Configuration Read the note at the bottom of this section, before "Autologin"
Last edited by WonderWoofy (2012-10-11 05:19:24)
Thanks, that's just what I was looking for.
I had read that but wasn't sure how it related to the new systemd way of doing things.
No longer confused. - Marking thread as [Solved].