Description of problem: # dnf remove fprintd-pam ... Running transaction Preparing : 1/1 Erasing : fprintd-pam-1.94.0-3.el9.x86_64 1/1 Running scriptlet: fprintd-pam-1.94.0-3.el9.x86_64 1/1 Unable to disable feature [2]: No such file or directory Verifying : fprintd-pam-1.94.0-3.el9.x86_64 1/1 Installed products updated. This is likely caused by postuninstall scriptlet (using /bin/sh): if [ $1 -eq 0 ]; then /bin/authselect disable-feature with-fingerprint || : fi which throws that error when there is no authselect profile selected: # authselect current No existing configuration detected. So I would suggest either throwing the error output away with 2>/dev/null, which would make sense since the exit code is already thrown away with || : Alternatively, check for the current profile before doing disable-feature, ie. if current=$(authselect current -r) && authselect list-features "$current" | grep -q with-fingerprint; then authselect disable-feature with-fingerprint fi Version-Release number of selected component (if applicable): fprintd-pam-1.94.0-3.el9
(In reply to Jiri Jaburek from comment #0) > which throws that error when there is no authselect profile selected: > > # authselect current > No existing configuration detected. How do you get into this state?
pbrezina, is there any reason why authselect is throwing a warning here? Is there a way to make this call quiet if fprintd-pam isn't used?
(In reply to Bastien Nocera from comment #4) > (In reply to Jiri Jaburek from comment #0) > > which throws that error when there is no authselect profile selected: > > > > # authselect current > > No existing configuration detected. > > How do you get into this state? This was filed over a year ago, so I don't remember anymore. But from what I can tell, authselect without any profile selected is the default after a fresh RHEL installation (at least for some minimal RHEL install). You (or some automation) would have to use "authselect select <profile>" to actually apply a specific profile.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.