Bug#462889: seahorse fails to start

[Jose Carlos Garcia Sogo]

On lun, 2008-01-28 at 22:01 +0100, Wolodja Wentland wrote:
> Package: seahorse
> Version: 2.20.3-1+b1
> Followup-For: Bug #462889
> 
> > Do you have a big (really BIG) public keyring? Do you have Debian 
> > keyring added in gpg.options file?
> 
> I am not sure what you consider a BIG public keyring, but mine is around 
> 12 MB and would be surprised if that qualifies as one.

Having into account that Debian one is ~24MB, I can tell you your one is
hughe for personal use.
THe problem is that seahorse tries to read all keys in your public
keyring to make a list of contacts, so it gets stuck. This is a known
problem, but people usually don't have more than 10-20 keys, and having
>200 keys is quite uncommon.
I don't know if there is a plan to try to fix this, but that would also
imply caching keys into something like a sqlite database, which produces
a security problem, as you can have changed how trusted a key is, and
seahorse won't notice till it scans all keys again 

> 
> > Could you try with a clean public keyring? And if the error still 
> > happens to you, with a clean private keyring? (please make backup 
> > copies of your keyrings, specially private one before testing)
> 
> After moving my ~/.gnupg folder somewhere else seahorse worked again. I
> could copy my private keyring back and migrated all important keys back 
> into my "new" public keyring. The problem still occurs with my old 
> pubring.gpg.
> 
> Thank you for the fast reply and kind help.
> 

No problem. I will leave the bug open, and perhaps tag it as wontfix.

> Wolodja Wentland
> 
>