GNOME Bugzilla – Bug 112403
Problems with multiple and large keyrings.
Last modified: 2004-12-22 21:47:04 UTC
I was adding the debian keyrings to .gnupg/gpg.conf with the following lines: keyring /usr/share/keyrings/debian-keyring.gpg keyring /usr/share/keyrings/debian-keyring.pgp Adding the keys show gives the following problems: 1. The startup time with those keyrings are quite long. 2. Having this ammount of keys also makes it hard to use seahorse without a search function. 3. It's not possible to see which keyring a key belongs to.
Seahorse uses gpgme as the backend, which currently offers no control of the actual key ring(s), just the loaded keys. I personally don't see much point to knowing what key ring a key is in, but there does need to be some visual cue for key pairs (#111176). If you'd like, I can put in a request to the gpgme devs regarding this. As for key listing, large key rings will take a long time because keys are loaded sequentially. If you can, please try using gpa to see if it is faster. Some of the slow down is due to redrawing the window. You can also try changing the value of the gconf setting /desktop/pgp/progress_update. Make it higher and there will be less redraws. Make it negative (or maybe 0) and there will be no redraws until finished. Please make any search related comments or requests in bug #111136.
I think I'm going to close this bug. 1. Solved by the background loading that seahorse currently does. 2. Search filter recently committed to CVS. 3. GPG is specific.