On 19-09-2014 17:02, Armin K. wrote: > On 19.9.2014 21:41, Fernando de Oliveira wrote: >>>>>> What I don't understand is that lxdm starts, but does not >>>>>> load polkit nor ConsoleKit.
Now it is loading polkit (in both machines) but not ConsoleKit (in one machine). >>>>> You need to explicitly include system-session into lxdm PAM file or >>>>> include consolekit pam module like done in systems-ession. >>>> >>>> Just to be sure we are talking about the same thing. LXSession is OK. >>>> However, LXDM, just started by the bootscript is unable of >>>> shutdown/reboot. Also, it is configured to show the users list. In my >>>> previous dev machine both work fine. Th the best of my searches, Both >>>> systems are equally configured. >>> What are the contents of /etc/pam.d/lxdm and /etc/pam.d/system-session >>> on both systems? >> >> The same, I really believe: >> >> fernando [ ~ ]$ hostname >> VMWLFS75eudev >> fernando [ ~ ]$ cat /etc/pam.d/lxdm >> #%PAM-1.0 >> auth required pam_unix.so >> auth requisite pam_nologin.so >> account required pam_unix.so >> password required pam_unix.so >> session required pam_unix.so > > As I said, it needs to use ConsoleKit's PAM module manually or include > system-session. Well this one is the machine working fine. It does not need to be fixed. The other doesn't work fine, needs a fix. But let's continue the discussion here. Forgive my ignorance, but I really don't understand: "it needs to use ConsoleKit's PAM module manually or include system-session". I tried to add the line account include system-account No difference. > You are good to copy config file from KDM (KDE Workspace) and try > again. I used your suggestion: $ cat /etc/pam.d/lxdm # Begin /etc/pam.d/lxdm auth requisite pam_nologin.so auth required pam_env.so auth required pam_succeed_if.so uid >= 1000 quiet auth include system-auth account include system-account password include system-password session include system-session # End /etc/pam.d/lxdm No difference. > PAM Module should fire up ConsoleKit when session is started unless > LXDM has a separate process for greeter that doesn't register any > session. When LXSession starts, *it does fire up ConsoleKit* in both machines. But I suppose that, as in the machine that works, LXDM should run ConsoleKit, before any user intervention, at the greeter, in order to have the privileges for shutdown/reboot. It does in one machine, but does not in the other. > >> fernando [ ~ ]$ cat /etc/pam.d/system-session >> # Begin /etc/pam.d/system-session >> >> session required pam_unix.so >> >> # End /etc/pam.d/system-session >> # Begin ConsoleKit addition >> >> session optional pam_loginuid.so >> session optional pam_ck_connector.so nox11 >> >> # End ConsoleKit addition >> >> >> >> fernando [ ~ ]$ hostname >> VMWLFS76 >> fernando [ ~ ]$ cat /etc/pam.d/lxdm >> #%PAM-1.0 >> auth required pam_unix.so >> auth requisite pam_nologin.so >> account required pam_unix.so >> password required pam_unix.so >> session required pam_unix.so >> fernando [ ~ ]$ cat /etc/pam.d/system-session >> # Begin /etc/pam.d/system-session >> >> session required pam_unix.so >> >> # End /etc/pam.d/system-session >> # Begin ConsoleKit addition >> >> session optional pam_loginuid.so >> session optional pam_ck_connector.so nox11 >> >> # End ConsoleKit addition >> >> -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
