Re: gnome-keyring keyring can't be unlocked, likely due to oversize

[xor <gnome idlecore com>]

As far as size is concerned, I just ran a test with 1200 items and over 
760kb and seahorse seemed to run fine, locked and unlocked without 
problem. I suggest you do the basics first, make sure seahorse is up to 
date, make sure the keyring file as read permission, a lot of the work 
on seahorse is done with libsecret, so make sure that one is up to date 
as well, also restart(1) gnome-keyring-daemon before testing again.

If you want to poke around a bit more, I suggest you use libsecret's 
Python bindings instead of gnomekeyring which is now a bit outdated.

(1) gnome-keyring-daemon --replace

On 27/08/16 01:44, Weiwu Zhang wrote:
> Hello.
>
> Seahorse can't unlock my keyring - right-click and select "unlock" has
> no effect, no terminal message either.
>
> I suspect the cause being oversize. My login.keyring is 760KB and have
> roughly 300 passwords in it.
>
> Gnome would automatically create a new keyring when I login, likely
> because it can't use the old login.keyring.
>
> python-gnomekeyring script (like this one¹) shows zero items in the
> oversized keyring.
>
> If oversize could be an issue, I hope I can split it into two and
> recover the passwords in it. Is there a known way to do so?
>
> Thanks in advance!
>
> Regards
>
> 1. https://blog.schmichael.com/2008/10/30/listing-all-passwords-stored-in-gnome-keyring/
> _______________________________________________
> gnome-keyring-list mailing list
> gnome-keyring-list gnome org
> https://mail.gnome.org/mailman/listinfo/gnome-keyring-list