Unfortunately, adding pam and gdm with ~x86 to keywords and remerging
only updated gdm and the problem still occurs with a potential
workaround, et > /dev/null 2>&1
Does this sound like a pam problem? gdm problem? or et (enemy territory)
itself perhaps?
once more running et caused a gdm restart
Jul 27 13:19:29 dsotm gdm[7898]: PAM unable to
dlopen(/lib/security/pam_console.so)
Jul 27 13:19:29 dsotm gdm[7898]: PAM [dlerror:
/lib/security/pam_console.so: cannot open shared object file: No such
file or directory]
Jul 27 13:19:29 dsotm gdm[7898]: PAM adding faulty module:
/lib/security/pam_console.so
after updating to gdm 2.8.0.1 still restarts
Jul 27 17:59:26 dsotm gdm[6359]: failsafe dialog failed (inhibitions: 0 0)
Jul 27 17:59:32 dsotm gdm[6359]: failsafe dialog failed (inhibitions: 0 1)
Jul 27 17:59:38 dsotm gdm[6359]: failsafe dialog failed (inhibitions: 1 1)
Jul 27 17:59:38 dsotm gdm[6359]: gdm_slave_xioerror_handler: Fatal X
error - Restarting :0
Jul 27 17:59:38 dsotm gdm(pam_unix)[6359]: session closed for user chris
George Roberts wrote:
Chris this may help with the problem:
http://forums.gentoo.org/viewtopic-t-350736-highlight-gdm+pam.html
Chris Fairles wrote:
Oddly enough, if I run et like this
et >> et.log 2>&1
it runs fine and gdm does not restart itself.
heres a snip from the log at least where I *think* it was failing
before... it tries to run a tty console which pam does not like, why?
--- Common Initialization Complete ---
Opening IP socket: localhost:27960
Hostname: dsotm
IP: 127.0.0.1
Started tty console (use +set ttycon 0 to disable)
thnx,
chris
Chris Fairles wrote:
Ran a emerge -NDuva world, updated a bunch of gnome stuff.
gnome-base/gnome-2.10-r1 and deps and
gnome-base/gdm-2.6.0.9-r2
Launching et (enemey territory) gives (in /var/log/messages)
Jul 26 22:58:13 dsotm gdm[23200]: PAM unable to
dlopen(/lib/security/pam_console.so)
Jul 26 22:58:13 dsotm gdm[23200]: PAM [dlerror:
/lib/security/pam_console.so: cannot open shared object file: No
such file or directory]
Jul 26 22:58:13 dsotm gdm[23200]: PAM adding faulty module:
/lib/security/pam_console.so
Jul 26 22:58:15 dsotm gdm(pam_unix)[23200]: session opened for user
chris by (uid=0)
Jul 26 22:58:23 dsotm su(pam_unix)[23301]: session opened for user
root by (uid=1000)
Jul 26 23:00:35 dsotm su(pam_unix)[23301]: session closed for user root
Jul 26 23:00:39 dsotm gdm[23200]: gdm_slave_xioerror_handler: Fatal
X error - Restarting :0
Jul 26 23:00:39 dsotm gdm(pam_unix)[23200]: session closed for user
chris
gdm restarts .... no game
I've tried commenting out all of
dsotm ~ # grep console /etc/pam.d/*
/etc/pam.d/gdm:session optional /lib/security/pam_console.so
/etc/pam.d/gdm-autologin:session optional /lib/security/pam_console.so
/etc/pam.d/xdm:session optional pam_console.so
/etc/pam.d/xserver:# Next line you need console ownership to be able
to start X
/etc/pam.d/xserver:#auth required pam_console.so
restarting gdm, even rebooting, same error as above.
tried setting USE="pam_console" emerge -Nva pam ... adding the login
pam_console, uncommenting all of the above lines, i just get the
Jul 26 22:41:05 dsotm gdm[8000]: gdm_slave_xioerror_handler: Fatal X
error - Restarting :0
i'm almost ready to USE="-pam" emerge -e world ...
chris
--
[email protected] mailing list
