After upgrading to pam from 1.30.0-r2 to 1.3.1 the gdm service doesn't start (it starts but I never get a display). Downgrading back to pam-1.30.0-r2 works around the issue. gdm log attached below. $ equery -q u =sys-libs/pam-1.3.1 -audit -berkdb -cracklib -debug -filecaps -nis +nls +pie -static-libs $ equery -q u gdm -accessibility -audit -branding -fprint +introspection +ipv6 -plymouth -smartcard -tcpd -test +wayland -xinerama $ emerge --info Portage 2.3.50 (python 3.6.6-final-0, default/linux/amd64/17.0/no-multilib, gcc-8.2.0, glibc-2.27-r6, 4.19.0-rc6 x86_64) ================================================================= System uname: Linux-4.19.0-rc6-x86_64-Intel-R-_Core-TM-_i7-8650U_CPU_@_1.90GHz-with-gentoo-2.6 KiB Mem: 16373520 total, 13417876 free KiB Swap: 16777212 total, 16777212 free Timestamp of repository gentoo: Tue, 02 Oct 2018 21:56:28 +0000 sh bash 4.4_p23 ld GNU ld (Gentoo 2.31.1 p3) 2.31.1 app-shells/bash: 4.4_p23::gentoo dev-lang/perl: 5.26.2::gentoo dev-lang/python: 2.7.15::gentoo, 3.6.6::gentoo dev-util/pkgconfig: 0.29.2::gentoo sys-apps/baselayout: 2.6-r1::gentoo sys-apps/sandbox: 2.13::gentoo sys-devel/autoconf: 2.69-r4::gentoo sys-devel/automake: 1.16.1-r1::gentoo sys-devel/binutils: 2.31.1-r1::gentoo sys-devel/gcc: 8.2.0-r3::gentoo sys-devel/gcc-config: 2.0::gentoo sys-devel/libtool: 2.4.6-r5::gentoo sys-devel/make: 4.2.1-r4::gentoo sys-kernel/linux-headers: 4.17::gentoo (virtual/os-headers) sys-libs/glibc: 2.27-r6::gentoo Repositories: gentoo location: /usr/portage sync-type: rsync sync-uri: rsync://blackwidow/portage priority: -1000 sync-rsync-verify-max-age: 24 sync-rsync-verify-jobs: 1 sync-rsync-verify-metamanifest: False sync-rsync-extra-opts: --filter="P .rsync-filter" marduk location: /var/lib/layman/marduk masters: gentoo priority: 50 ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="* -@EULA AdobeFlash-11.x google-chrome google-talkplugin Google-TOS Google-TOS AdobeFlash-11.x" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-march=native -O2 -pipe" DISTDIR="/var/portage/distfiles" EMERGE_DEFAULT_OPTS=" --autounmask=n --jobs --keep-going --misspell-suggestions=n --oneshot --quiet-build --quiet-unmerge-warn --usepkg --with-bdeps=n --jobs=4 --getbinpkg --rebuilt-binaries=y --binpkg-respect-use --binpkg-changed-deps" ENV_UNSET="DBUS_SESSION_BUS_ADDRESS DISPLAY PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs binpkg-multi-instance buildpkg cgroup config-protect-if-modified distlocks fixlafiles multilib-strict news noinfo notitles parallel-fetch parallel-install preserve-libs protect-owned sandbox sfperms skiprocheck strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://distfiles.gentoo.org" LANG="en_US.utf8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" LINGUAS="" MAKEOPTS="-j9" PKGDIR="/var/portage/packages" PORTAGE_BINHOST="http://blackwidow/packages/lighthouse/" PORTAGE_COMPRESS="" PORTAGE_COMPRESS_FLAGS="" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_EXTRA_OPTS="--filter="P .rsync-filter"" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git" PORTAGE_TMPDIR="/var/tmp" USE="acl aes amd64 asm avx avx2 f16c fma3 glamor introspection ipv6 mmx mmxext nls opentype pam pclmul popcnt split-usr sse sse2 sse3 sse4_1 sse4_2 ssse3 systemd udev unicode utf8 wayland xattr" ABI_X86="64" APACHE2_MODULES="authn_core authz_core authz_host authz_user unixd socache_shmcb auth_digest authn_file authz authz_groupfile dav dav_fs dir group_file mime" APACHE2_MPMS="prefork" CAMERAS="*" CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" CURL_SSL="openssl" ELIBC="glibc" FFTOOLS="*" GRUB_PLATFORMS="pc" INPUT_DEVICES="libinput" KERNEL="linux" LLVM_TARGETS="X86" NGINX_MODULES_HTTP="auth_basic gzip proxy rewrite uwsgi" PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" RUBY_TARGETS="ruby25" USERLAND="GNU" VIDEO_CARDS="intel i965" Unset: CC, CPPFLAGS, CTARGET, CXX, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND
Created attachment 549052 [details] output from `journalctl -b -u gdm.log`
Also breaks .bashrc xorg "autostart" after tty login. I have the following in my .bashrc: if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then export XSESSION="i3wm" export XCURSOR_SIZE=48 export TERMINAL="alacritty" exec startx; exit fi With pam-1.3.1 this is no longer executed. After downgrading to pam-1.3.0-r2 startx via bashrc works OK.
Created attachment 549130 [details] journalctl -b output It also breaks sway, specifically wlc. When I try to start sway from the tty (which is what I usually do), it fails with [main.:48] Not running from X11 and no access to /dev/input/event0 or logind unavailable indicating that session authentication failed. `journalctl -b` then gave me the log that is attached, indicating various modules - principally `pam_systemd.so` - that PAM-1.3.1 fails to find (starting at line 803). Curiously enough, these libraries are in /lib/security, not /usr/lib64/security, and PAM-1.3.0 finds them without problem. Is there a change in PAM-1.3.1 that has not been announced?
1.3.1 also breaks pam_mount, it's probably the same underlying reason. pam_mount works by adding an optional module to system-auth, so I guess there's a generic problem in loading external modules.
The tree already has the fix, just I do not know what was your sync method, try to sync again and reinstall pam :)
Thanks for the fix!
I had the same issue with gdm as initially reported here. I took me some time to narrow this down to this closed issue with pam. Since I apparently emerged the pam-1.3.1 that was affected by the reported issue, after plainly remerging pam-1.3.1 again, the issue is gone for me as well. So, a revbump would have been nice :)
(In reply to Martin Wegner from comment #7) > I had the same issue with gdm as initially reported here. > > I took me some time to narrow this down to this closed issue with pam. Since > I apparently emerged the pam-1.3.1 that was affected by the reported issue, > after plainly remerging pam-1.3.1 again, the issue is gone for me as well. > > So, a revbump would have been nice :) I agree, this should have been a revbump. I upgraded pam on another system a few days ago and didn't experience any immediate issues. Then today I rebooted the system and was having issues with systemd. It took me a while to realize that maybe I need to rebuild pam. I think other users will encounter a similar issue, where they update pam and see no issues, then a few days or months or more down the road they reboot and have issues, and not see this bug report (because it's closed or they didn't know to search pam). I revbump would have ensured that pam gets rebuilt.
*** Bug 667652 has been marked as a duplicate of this bug. ***
*** Bug 667998 has been marked as a duplicate of this bug. ***
Can this be revbumped please - it's caused quite a few issues on 3 of my systems - it's the easiest way to make sure everyone has the fix
