Red Hat Bugzilla – Bug 1478698
Seahorse does only show errors, cannot save in keyring
Last modified: 2017-08-06 05:02:07 EDT
Description of problem: Application cannot access keyring, when trying to unlock the passwords in seahorse I get "Cannot unlock: Wrong password or PIN."
Seahorse was not adjusted and was just configured to use the login password to unlock itself.
So I deleted (aka renamed) the keyring data files in to reset ~/.local/share/keyrings. Still, however, afterwards applications cannot save passwords in the keyring. The user.keystore file stays empty and no other file is created.
Version-Release number of selected component (if applicable): 3.20.0
How reproducible: don't know
What could have been a problem:
1. I use LUKS for FDE, don't know how/whether this (still) influences seahorse, see https://bugzilla.redhat.com/show_bug.cgi?id=1406509
2. I switched between X and Wayland some times at login.