Some news about status of ConsoleKit and Display Managers in Portage
pambase-20101024-r2 will restore the same behavior as pambase-20101024
had; it will restore the 'nox11' argument to the pam_ck_connector.so
line in /etc/pam.d/system-login.
this pam_ck_connector.so module is now used only for console logins
because all of the display managers we ship, have native ConsoleKit
xdm since 1.1.11-r1
slim since 1.3.2-r7
lxdm, all versions
gdm, all versions
kdm, all versions
lightdm, all versions
enter, lastrited now
in practise this means you don't need the CONFIG_AUDITSYSCALL in kernel
for any of these display managers, or worry about pam_ck_connector.so at
it also means you don't need to manually put 'ck-launch-session'
anywhere in your configs, except when using startx with custom .xinitrc.
and even startx works if you have XSESSION exported and no .xinitrc
without adding ck-launch-session anywhere yourself.
in otherwords, everything will just work(tm).
long as people now remember to punt any custom trickery they might have
added before we reached this point.