Description of problem: Not all authselect profiles may have the with-ecryptfs feature. Additionally, systems that have not run authselect will also error out if this is run. Version-Release number of selected component (if applicable): ecryptfs-utils-111-29.fc38 How reproducible: 100% Steps to Reproduce: 1. install ecryptfs-utils on a host without authselect profile with-ecryptfs feature 2. 3. Actual results: post script errors out Expected results: no error Additional info: https://src.fedoraproject.org/rpms/ecryptfs-utils/pull-request/3
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
Could you give me an example of authselect profile that does not allow ecryptfs feature? Also what do you mean by systems that have not run authselect will also error out? I've tried fresh fedora installation and everything worked fine. Also there is a strong authselect requirement, so you can't easily have a system without authselect (util-linux - pam,sudo - authselect) being installed.
The behavior manifests in the %post scripts. One of my local profiles doesn't implement `with-ecryptfs`, however, the %post{un} scripts run `authselect {enable,disable}-feature with-ecryptfs` automatically. This results in an error and causes RPM to complain. Adding an `|| true` lets the official profiles do their thing without forcing me to add support for something I'm not using in my downstream profile. I believe https://src.fedoraproject.org/rpms/ecryptfs-utils/pull-request/3#request_diff is all that is required to resolve the issue.
Seems my previous comment disappeared (or more likely I wrote it under different bug, but can't find it right now)... Anyway, I will be brief this time. Packages in Fedora should work out of the box. All Fedora supplied profiles support ecryptfs. The pull request above would fix the issue for you, but it would hide potential problem for other users. Fail early approach is much better than spending a lot of time debugging an issue. So I won't use the pull request, but I came up with a solution that should allow ecryptfs with configurations not using login automount. I've split ecryptfs-utils to new subpackage ecryptfs-utils-loginmount that contains the authselect configuration and main package has it as a weak dependency, so you don't have to install it if you don't want.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
FEDORA-2025-ca334737c8 (ecryptfs-utils-111-41.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ca334737c8
FEDORA-2025-deb30beb17 (ecryptfs-utils-111-41.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-deb30beb17
FEDORA-2025-deb30beb17 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-deb30beb17` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-deb30beb17 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-ca334737c8 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ca334737c8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ca334737c8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-ca334737c8 (ecryptfs-utils-111-41.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-deb30beb17 (ecryptfs-utils-111-41.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.