Re: [trinity-devel] Bug 1902 - pam.d and preprocessor checks surrounding consolekit may be part of issue

On 02/25/2014 12:03 AM, François Andriot wrote: Thank you Francios, On Arch the only pam file was /etc/pam.d/trinity: /etc/pam.d/trinity #%PAM-1.0 auth required pam_securetty.so auth requisite pam_nologin.so auth include system-local-login account include system-local-login session include system-local-login I updated it to test the Arch kde4 /apm file: #%PAM-1.0 auth include system-login account include system-login password include system-login session include system-login However, that made no difference (system-local-login is just an alias of system-login). There was no 'kdescreensaver' in the Arch TDE install, so I created a 'tdescreensaver' pam file: /etc/pam.d/tdescreensaver #%PAM-1.0 auth required pam_unix_auth.so Again, it made no difference. I have poked around the mkpamserv executable and think I can patch it for arch to generate the tdescreensaver file on tdebase install, but I'm still not clear on how/where in the code to insure the name 'tdescreensaver' will be recognized as a pam file by the system. (the inter-workings of pam are a learning experience as well). I'll test with your config and report back. If you get the process tracking figured out, let me know. Thanks. -- David C. Rankin, J.D.,P.E.