Description of problem & possible fix: While there are lots of issues with full user home directory encryption in Fedora, this one is fairly straightforward to fix. In `/etc/pam.d/sddm` there are currently these lines (among others): … session required pam_namespace.so session include password-auth -session optional pam_gnome_keyring.so auto_start -session optional pam_kwallet5.so -session optional pam_kwallet.so session include postlogin While this may seem sensible, it breaks down in case of the pam_ecryptfs.so module which is part of `/etc/pam.d/postlogin`; by the time `pam_ecryptfs.so` does it's overlay mounting thing, gnome keyring & kwallet have long given up on looking for their respective files and the respective password stores will remain locked. The solution is therefore to simply make unlocking password stores the very last thing to happen upon session initialization: … session required pam_namespace.so session include password-auth session include postlogin -session optional pam_gnome_keyring.so auto_start -session optional pam_kwallet5.so -session optional pam_kwallet.so Then it works as expected 😀 Version-Release number of selected component (if applicable): 0.14.0 How reproducible: Always Steps to Reproduce: 1. Set SELinux to permissive mode (told there are lot of issues with `ecryptfs` on Fedora currently) and reboot 2. Create a new user account and log in and open `seahorse` / `kwalletmanager5` to create the respective password storage, then log out again 3. From a virtual console run `ecryptfs-migrate-home --user $USER` as root 4. Also add the user to the `ecryptfs` group 5. After the migration completes log in and open `seahorse` or `kwalletmanager5` Expected results: No password prompt, log in password is used to decrypt the password store. Actual results: A password prompt, errors in `journalctl`.
Thanks for the excellent detective-work
Unfortunately the solution I posted doesn't always seem work (and I'm not sure why, yet). I'll add a new comment once I've figured out when and why it fails at time.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.