On 03.10.2012 20:58, Ragnar Thomsen wrote: > On Monday 01 October 2012 22:05:39 Armin wrote: >> If you need anything else, just ask. > > By re-installing consolekit, polkit and upower to get the service files > installed, my system is now functional. > > I also needed to reinstall pulseaudio to fix my sound. > > One thing that was not working, was authenticating to perform root actions in > KDE. I tracked this down to a polkit issue. After re-installing polkit it uses > logind instead of consolekit, and logind didn't get started and hence no > session management. I managed to fix this by adding: > > session optional pam_systemd.so kill-session-processes=1 > > to the kde pam file. Now I can authenticate as root in KDE, but this only > works when booting using KDM. When booting into console and then starting KDE > by the startx command, logind doesn't get started. > Is there a way to start logind in the .xinitrc file, similar to the ck-launch- > session command? > > -Ragnar- >
In BLFS ConsoleKit configuration we append ConsoleKit stuff into system-session config file. This is my system-session $ cat /etc/pam.d/system-session # Begin /etc/pam.d/system-session session required pam_unix.so # Uncomment if consolekit is installed. session required pam_loginuid.so session optional pam_ck_connector.so nox11 # Uncomment if systemd is installed. session optional pam_systemd.so # End /etc/pam.d/system-session So the answer is, just add pam_systemd to system-session. Do note that sudo might get broken if it sources system session. In that case just use "session required pam_unix.so" in /etc/pam.d/sudo instead of including system-session. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
