gnome-screensaver fails to auth when built with pam to return to desktop. Not sure where exactly in the pam auth it is failing if someone wishes to point out a way to retrieve a more specific issue let me know. Reproducible: Always Portage 2.1.3_rc7 (default-linux/x86/2007.0, gcc-4.2.0, glibc-2.6-r0, 2.6.22-rc7-ck1 i686) ================================================================= System uname: 2.6.22-rc7-ck1 i686 Intel(R) Pentium(R) 4 CPU 3.06GHz Gentoo Base System release 1.12.10 Timestamp of tree: Mon, 09 Jul 2007 13:30:01 +0000 ccache version 2.4 [disabled] dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r7 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17.50.0.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.22 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=prescott -ftracer -fprefetch-loop-arrays -pipe -fforce-addr" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=prescott -ftracer -fprefetch-loop-arrays -pipe -fforce-addr" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict unmerge-orphans" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_US.UTF-8" LC_ALL="en_US.utf8" LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/gentoo" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow 3dnowext X a52 aac acpi alsa berkdb branding bzip2 cdr cpudetection cracklib crypt cups dbus dri dvd dvdr dvdread encode ffmpeg firefox gdm gif gnome gtk hal jpeg mad mmx mmxext moznopango mp3 ncurses nptl nptlonly nsplugin nss ogg opengl pam perl pic png python readline sdl spell sse sse2 ssl svg tcpd tiff unicode vorbis x264 x86 xinerama xorg xv xvid zlib" ALSA_PCM_PLUGINS="copy linear route mulaw alaw adpcm rate plug multi shm file null empty share meter hooks lfloat ladspa dmix dshare dsnoop asym iec958 softvol extplug ioplug" ELIBC="glibc" INPUT_DEVICES="mouse keyboard" KERNEL="linux" USERLAND="GNU" VIDEO_CARDS="i915 i810 v4l" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
first, please specify which version of gnome-screensaver shows this problem then try with CFLAGS="-O2 -march=prescott" finaly, in a terminal, make sure there is no gnome-screensaver launched and start it with --no-daemon --debug. Please check system log as well as there should be a trace of what's wrong with pam.
Created attachment 124429 [details] debug info Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM unable to dlopen(<*unknown module path*>) Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM [error: <*unknown module path*>: cannot open shared object file: Too many open files] Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM adding faulty module: <*unknown module path*> Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM unable to dlopen(/lib/security/pam_deny.so) Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM [error: /lib/security/pam_deny.so: cannot open shared object file: Too many open files] Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM adding faulty module: /lib/security/pam_deny.so Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM unable to dlopen(/lib/security/pam_permit.so) Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM [error: /lib/security/pam_permit.so: cannot open shared object file: Too many open files] Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM adding faulty module: /lib/security/pam_permit.so Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM unable to dlopen(<*unknown module path*>) Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM [error: <*unknown module path*>: cannot open shared object file: Too many open files] Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM adding faulty module: <*unknown module path*> Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM unable to dlopen(/lib/security/pam_deny.so) Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM [error: /lib/security/pam_deny.so: cannot open shared object file: Too many open files] Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM adding faulty module: /lib/security/pam_deny.so Might better turn this over to the pam team.
did you by any chance updated pam recently ? you might want to have a look at: http://www.gentoo.org/proj/en/base/pam/upgrade-0.99.xml adding pam herd so they can have a look.
Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth sounds clear enough to me at this point: the file is inaccessible or missing. Why, not sure :)
(In reply to comment #4) > Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM _pam_load_conf_file: > unable to open /etc/pam.d/system-auth > > sounds clear enough to me at this point: the file is inaccessible or missing. > Why, not sure :) > Umm no I would not say it is clear as permissions are sane. [anarchy - ~] ls -l /etc/pam.d/system-auth -rw-r--r-- 1 root root 447 2007-07-09 19:46 /etc/pam.d/system-auth content of file cat /etc/pam.d/system-auth #%PAM-1.0 auth required pam_env.so auth sufficient pam_unix.so try_first_pass likeauth nullok auth required pam_deny.so account required pam_unix.so password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 try_first_pass retry=3 password sufficient pam_unix.so try_first_pass use_authtok nullok md5 shadow password required pam_deny.so session required pam_limits.so session required pam_unix.so
Does gnome-screensaver run chrooted by chance?
(In reply to comment #6) > Does gnome-screensaver run chrooted by chance? > No it does not run chrooted.
(In reply to comment #2) > Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM [error: <*unknown module > path*>: cannot open shared object file: Too many open files] > Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM [error: > /lib/security/pam_deny.so: cannot open shared object file: Too many open > Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM [error: > /lib/security/pam_permit.so: cannot open shared object file: Too many open > files] > Jul 9 19:32:55 crazier gnome-screensaver-dialog: PAM [error: > /lib/security/pam_deny.so: cannot open shared object file: Too many open files] Uhm... cat /proc/sys/fs/file-max cat /proc/sys/fs/file-nr
don't play with /etc/limits and the likes if you can't analyze the consequences.
ok, Bugs Bunny sent me a mail : "Bug is not invalid. It is caused when pam is linked to audit if you noticed my bugzilla account is locked so I can not respond to the bug. But once again a gentoo dev has no clue and assumes." I'll pass on the no clue. If somebody has an audit setup that would be interesting to hear from you. If pam herd has a clue, please speak.
(In reply to comment #10) > Bug is not invalid. It is caused when pam is linked to audit if you > noticed my bugzilla account is locked so I can not respond to the bug. > But once again a gentoo dev has no clue and assumes." No such thing available in the tree. Custom ebuilds such as Bug 184519 -> INVALID.
(In reply to comment #11) > (In reply to comment #10) > > > Bug is not invalid. It is caused when pam is linked to audit if you > > noticed my bugzilla account is locked so I can not respond to the bug. > > But once again a gentoo dev has no clue and assumes." > > No such thing available in the tree. Custom ebuilds such as Bug 184519 -> > INVALID. > This is not my bug so I can not reopen it but as the original reporter pointed out when pam is linked to audit gnome-screensaver fails to auth. It has nothing to do with custom ebuilds. This is just another breakage that can be fixed when bug http://bugs.gentoo.org/show_bug.cgi?id=189669 is fixed.
In my case (another program, but the same error messages) this happened afrer upgrade of 'pam' because 'pambase' wasn't installed. After I had installed the 'pambase' package, it created the necessary '/etc/pam.d/system-auth' and '/etc/pam.d/other' files. Everything went fine since then.
