Add script to avoid fingerprint-auth issues for long term Fedora users
sudo dnf upgrade --refresh --advisory=FEDORA-2021-48ca6e6b86
This update has been submitted for testing by ipedrosa.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update has been pushed to testing.
Freezes the system once the scriptlet starts. To make sure it wasn't an accident, I restored a clonezilla image.
Same results ... system freezes.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
I've tested it with a freshly installed Fedora 34 VM and the update seems to work under several circumstances. So, can you provide some feedback from your system? Which version of Fedora are you using?
What's the output of "ls -l /etc/pam.d/fingerprint-auth"?
Does "/etc/pam.d/fingerprint-auth" contain "auth sufficient pam_fprintd.so" or something similar?
$ cat /etc/os-release
VERSION="34 (Workstation Edition)"
PRETTY_NAME="Fedora 34 (Workstation Edition)"
$ ls -l /etc/pam.d/fingerprint-auth
lrwxrwxrwx. 1 root root 32 8. Apr 11:03 /etc/pam.d/fingerprint-auth -> /etc/authselect/fingerprint-auth
Update @ipedrosa - I restored the image again and this time I updated all other packages before upgrading pam :
sudo dnf upgrade --enablerepo=updates-testing --exclude=pam
sudo dnf upgrade --enablerepo=updates-testing pam
Now it worked as expected, no system freeze. So it must have been an interference with another package update.
This update can be pushed to stable now if the maintainer wishes
Thanks for verifying that! Not sure how a freeze might occur, but the PAM scriptlet really shouldn't be causing any issues.
This fixes BZ#1942443 for me on Silverblue 34, upgraded from 33.
@clnetbox thanks for verifying it again!
You're welcome @benzea and @ipedrosa ! :)
@clnetbox the hang you hit may have been this one, if you have ibus packages installed:
openQA tests look good.
BTW, can we have this change on Rawhide too?
Do we have rawhide users with the problem?
In principle we should only need to run the added script once during the F33 -> F34 upgrade process. So my take was to not add the scriptlet to F35.
We explicitly allow and support upgrades across two release versions, for people who don't want to upgrade every six months. So F33 direct to F35 upgrade is a supported/release blocking operation. There will be people out there who expect to be able to upgrade from F33 to F35.
One thing I note about the scriptlet, BTW, is it doesn't check whether the symlink target actually exists. If I make /etc/pam.d/fingerprint-auth a dangling symlink, I do get an error during update:
Running scriptlet: pam-1.5.1-5.fc34.x86_64
/usr/bin/grep: /etc/pam.d/fingerprint-auth: No such file or directory
I don't think it's a big issue, though.
This update has been submitted for stable by adamwill.
I'll port the change to rawhide as proposed by @adamwill
This update has been pushed to stable.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2022 Red Hat, Inc. and
bodhi-server 6.0.1 on
bodhi is Free Software.
if you have any problems. Read the documentation.