Bug#684432: SELinux is the Reason

2012-11-05 Thread paul . szabo
Sorry, seems I spoke too soon. After commenting out selinux from the /etc/pam.d/gdm3 file I "know" I rebooted and seen the greeter come alive. But then, on further reboots, it (again, still) does not work. I still need Atl-Ctrl-Backspace to kill that very first X server, so subsequent gdm-session-

Bug#684432: SELinux is the Reason

2012-11-05 Thread Laurent Bigonville
Le Tue, 6 Nov 2012 09:59:05 +1100, paul.sz...@sydney.edu.au a écrit : > > ... the reason was identified to be pam_selinux.so plugged through > > /etc/pam.d/gdm3-autologin ... > > I do not use autologin. Instead I commented out the selinux lines > in /etc/pam.d/gdm3 and now the very first gdmgreet

Bug#684432: SELinux is the Reason

2012-11-05 Thread paul . szabo
> ... the reason was identified to be pam_selinux.so plugged through > /etc/pam.d/gdm3-autologin ... I do not use autologin. Instead I commented out the selinux lines in /etc/pam.d/gdm3 and now the very first gdmgreeter (after reboot) works. Thanks! Thanks, Paul Paul Szabo p...@maths.usyd.edu.

Bug#684432: SELinux is the Reason

2012-11-05 Thread Anton Martchukov
Based on IRC discussion the reason was identified to be pam_selinux.so plugged through /etc/pam.d/gdm3-autologin that produces: gdm-welcome][5739]: DEBUG(+): GdmSessionWorker: received pam message of type 2 with payload 'Would you like to enter a security context? [N] ' interactive prompt. On my