Bug 1015742
Summary: | Cannot create new keyring or open existing keyring files | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James <fedorabugmail> |
Component: | gnome-keyring | Assignee: | Matthias Clasen <mclasen> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | debarshir, mclasen, stefw, walters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-07 09:36:47 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James
2013-10-05 04:13:11 UTC
So killing the mate-keyring-daemon process, deleting the keyring and making a new keyring seems to work. Overwriting the file in .local/share/keyrings with my old file, restarting Seahorse and entering my old login password unlocked the keyring. It seems to understand it is a login keyring, but it isn't using my current login password. ~/.local/share/keyrings is the new location for keyrings, in compliance with the XDG Basedir spec. However, if ~/.gnome2/keyrings exists then it is used instead as a compatibility measure. I hope that clears things up. |