Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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?
(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.
Comment 8RHEL Program Management
2023-07-19 07:28:15 UTC
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.