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 rest
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
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
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[2
4 matches
Mail list logo
