Description of problem: Since last serie of updates, sudo and su are broken: [dhill@knox log]$ sudo -i Segmentation fault (core dumped) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: openat(AT_FDCWD, 0x7f3bcd9daa90, O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, 0x7f3bcd9d2c02, 0x7f3bcda0a5e0, AT_EMPTY_PATH) = 0 mmap(NULL, 223542144, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f3bc026f000 close(3) = 0 openat(AT_FDCWD, 0x7f3bcd9d4167, O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, 0x7f3bcd9d2c02, 0x7ffdc1c57bb0, AT_EMPTY_PATH) = 0 newfstatat(3, 0x7f3bcd9d2c02, 0x7ffdc1c579d0, AT_EMPTY_PATH) = 0 read(3, 0x55c310654660, 4096) = 3494 lseek(3, -2225, SEEK_CUR) = 1269 read(3, 0x55c310654660, 4096) = 2225 close(3) = 0 stat(0x7f3bcdd572e7, 0x7ffdc1c57ac0) = 0 openat(AT_FDCWD, 0x7f3bcdd572e7, O_RDONLY) = -1 EACCES (Permission denied) geteuid() = 1000 geteuid() = 1000 access(0x7ffdc1c56c80, X_OK) = -1 ENOENT (No such file or directory) access(0x7ffdc1c56c80, X_OK) = -1 ENOENT (No such file or directory) access(0x7ffdc1c56c80, X_OK) = -1 ENOENT (No such file or directory) access(0x7ffdc1c56c80, X_OK) = 0 stat(0x7ffdc1c56c80, 0x7ffdc1c56bf0) = 0 openat(AT_FDCWD, 0x7ffdc1c56760, O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, 0x7f3bcd9d2c02, 0x7ffdc1c56590, AT_EMPTY_PATH) = 0 read(3, 0x55c310655f00, 4096) = 2998 read(3, "", 4096) = 0 close(3) = 0 openat(AT_FDCWD, 0x55c310655f70, O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, 0x55c310656180, O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, 0x55c310656000, O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, 0x55c310656100, O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, 0x55c310656210, O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, 0x55c310656080, O_RDONLY) = -1 ENOENT (No such file or directory) write(2, 0x7ffdc1c58a60, 4sudo) = 4 write(2, 0x7f3bcdd5702e, 2: ) = 2 write(2, 0x7ffdc1c545e0, 133effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?) = 133 ioctl(2, TCGETS, 0x7ffdc1c56580) = 0 ) = 1a094c3, 1 write(2, 0x7f3bcda094c3, 1 ) = 1 exit_group(1) = ? +++ exited with 1 +++
[ 403.864584] sudo[5194]: segfault at 0 ip 00007f291015a2d5 sp 00007ffc31ba1758 error 4 in libc-2.32.9000.so[7f291001f000+14e000]
2020-12-08T21:34:06-0500 SUBDEBUG Upgrade: glibc-all-langpacks-2.32.9000-19.fc34.x86_64 2020-12-08T21:34:08-0500 SUBDEBUG Upgrade: glibc-common-2.32.9000-19.fc34.x86_64 2020-12-08T21:34:08-0500 SUBDEBUG Upgrade: glibc-langpack-en-2.32.9000-19.fc34.x86_64 2020-12-08T21:34:08-0500 SUBDEBUG Upgrade: glibc-2.32.9000-19.fc34.x86_64 2020-12-08T21:34:15-0500 SUBDEBUG Upgrade: glibc-headers-x86-2.32.9000-19.fc34.noarch 2020-12-08T21:34:16-0500 SUBDEBUG Upgrade: glibc-devel-2.32.9000-19.fc34.x86_64 2020-12-08T21:34:22-0500 SUBDEBUG Upgrade: glibc-2.32.9000-19.fc34.i686 2020-12-08T21:34:22-0500 SUBDEBUG Upgraded: glibc-devel-2.32.9000-18.fc34.x86_64 2020-12-08T21:34:22-0500 SUBDEBUG Upgraded: glibc-2.32.9000-18.fc34.i686 2020-12-08T21:34:22-0500 SUBDEBUG Upgraded: glibc-headers-x86-2.32.9000-18.fc34.noarch 2020-12-08T21:34:24-0500 SUBDEBUG Upgraded: glibc-all-langpacks-2.32.9000-18.fc34.x86_64 2020-12-08T21:34:24-0500 SUBDEBUG Upgraded: glibc-common-2.32.9000-18.fc34.x86_64 2020-12-08T21:34:24-0500 SUBDEBUG Upgraded: glibc-langpack-en-2.32.9000-18.fc34.x86_64 2020-12-08T21:34:24-0500 SUBDEBUG Upgraded: glibc-2.32.9000-18.fc34.x86_64
hi this is duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1905667
Let me see if masking fprintd.service helps.
It does help... now I have this : ~~~ [dhill@knox ~]$ sudo -i [sudo] password for dhill: dhill is not in the sudoers file. This incident will be reported. ~~~ which is ... better .
But, pam_fprintd is configured as auth sufficient pam_fprintd.so in pam. Shouldn't that mean that even if it rejects the authentication attempt, you can still continue with another method?
Seems to be a duplicate of #1906066 *** This bug has been marked as a duplicate of bug 1906066 ***