Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 1
    Likewise, on Debian 10 (Buster). Commented Nov 16, 2019 at 22:49
  • Had a similar problem on the latest Manjaro after restoring from a backup. Thank you! Commented Feb 9, 2022 at 18:57
  • Nothing appeared in seahorse after creating this dir in Debian 11 Commented Mar 18, 2023 at 20:04
  • In my case I already had this folder, but it turns out is got corrupted (by a faulty drive I've since moved away from). In my case I deleted it, recreated it, and then restored its permissions with chmod 700 keyrings. After that the problem went away. Thanks for pointing me in the right direction! Commented Apr 2, 2024 at 0:26
  • Thanks for this. I was headed in this direction anyway but this answer got me to try recreating .local/share/keyrings early. I was trying to figure out why Evolution would not stop prompting me to create a new default keyring after restoring from a backup, even after a reinstall and OS restart. Turns out I deleted .local/share/keyrings and apparently gnome-*/Evolution took its absence personally. Commented Aug 17, 2024 at 1:06