On Do, 2007-01-18 at 11:25 +0000, Sam Morris wrote: > On Thu, 2007-01-18 at 11:59 +0100, Sebastian Dröge wrote: > > I can't reproduce your lockup here. I sometimes get bug #401474 though > > when viewing key properties but the CPU usage goes down again after some > > seconds. > > > > Could it be that your lockup is just bug #401474? The UI isn't really > > responsive while taking 100% CPU and I could imagine that under some > > circumstances this looks like a lockup. Or is your lockup with ~0% CPU > > usage? > > Oops, I gave the wrong bug number. I'm actually running into #395814 > (slowness on key properties trust tab). I meant to investigate it more > thoroughly but I haven't had the time this week, plus #395814 is really > annoying, plus Seahorse seems to start downloading the public keys of > every unknown signature on the uids in my keyring, which takes some time > to undo after I realise what has happened (I keep forgetting to backup > my keyring before running it). :)
Do you have "keyserver-options auto-key-retrieve" in your ~/.gnupg/gpg.conf? Otherwise seahorse shouldn't download all signature-keys of the key... hm, I think it might be a good idea to forward this upstream in that case as this could lead to having almost the complete content of the keyservers in your keyring :) It could be that seahorse locks up either because of too many keys in the keyring (i.e. no lockup but takes forever to do something) or because the network traffic is done synchronous in the main thread. Anyway, I'll talk with upstream later :) Bye
signature.asc
Description: This is a digitally signed message part
