Bug 1478698 - Seahorse does only show errors, cannot save in keyring
Seahorse does only show errors, cannot save in keyring
Status: NEW
Product: Fedora
Classification: Fedora
Component: seahorse (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-08-06 05:02 EDT by rugk
Modified: 2017-08-06 05:02 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description rugk 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.

Note You need to log in before you can comment on or make changes to this bug.