GNOME Bugzilla – Bug 763891
gnome-keyring-daemon: failed to parse keyring: /home/user/.local/share/keyrings/login.keyring
Last modified: 2018-08-03 19:51:26 UTC
Hello and good day, I need some urgent help. gnome-keyring-daemon cannot read my keyring "login". What I did: - I already had 2 keyrings: the default login and another non-default one. - Created a new keyring and gave it a password. - Unlocked it and checked the box "automatically unlock on login" - after that action my default login-keyring was gone The login.keyring (~/.local/share/keyrings/login.keyring) is still there and above 100kb in size - so it's there. Of course I have backups. I tried to restore the whole "~/.local/share/keyrings" folder with no success. The other keyring is still working though - just not my default one. That's the output of journalctl when I restart the gnome-keyring-daemon: $ gnome-keyring-daemon --replace Mär 18 18:38:19 computername gnome-keyring-daemon[5812]: GLib: g_hash_table_unref: assertion 'hash_table != NULL' failed Mär 18 18:38:19 computername gnome-keyring-daemon[5812]: GLib: g_hash_table_unref: assertion 'hash_table != NULL' failed Mär 18 18:38:19 computername gnome-keyring-daemon[5812]: GLib: g_hash_table_unref: assertion 'hash_table != NULL' failed Mär 18 18:38:19 computername gnome-keyring-daemon[5812]: GLib: g_hash_table_unref: assertion 'hash_table != NULL' failed Mär 18 18:38:19 computername gnome-keyring-daemon[5812]: failed to parse keyring: /home/user/.local/share/keyrings/login.keyring I hope someone has some experience with this or knows where I can ask elsewhere.
Well a Backup from my first Deja-Dup a few weeks ago works. I guess the newest backup didn't include the file login.keyring - but I haven't checked it. For me it's solved for now - but there is an evil bug somewhere.
Changed product to seahorse since the corruption of my login.keyring happened there.
This also happened to me once and was able to repeat it. I recovered the contents of the keyring with the “dump-keyring0-format” program [1]. I was trying to create a program to list the keyrings using libsecret and made some changes using seahorse. The following error was returned when calling “secret_service_get_sync” after performing similar steps as the ones in the description of this bug report: “No such secret item at path: /org/freedesktop/secrets/collection/login/3” I had the “login” keyring with two items and then added another password keyring and modified the “automatically unlock” box before this happening. I'm using seahorse 3.20.0 [1] https://git.gnome.org/browse/gnome-keyring/plain/pkcs11/secret-store/dump-keyring0-format.c
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/150.