GNOME Bugzilla – Bug 606268
cannot create PGP keys
Last modified: 2010-07-19 20:23:22 UTC
This bug was already reported on launchpad (https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/493473) Seahorse seems not to create PGP keys. In fact after you select file -> new ... -> PGP Key -> (fill in "Full Name, email Address, comment and let the other advanced key options by default, that is Encryption Type DSA Elgamal, key strength 768 and expiration date to never expires") -> (enter a passphrase) a pop-up window appears showing the generating key "primegen" but then it never stops. Here .xsession_errors errors when I follow the above procedure ** (seahorse:1588): CRITICAL **: egg_datetime_set_clamp_date: assertion `minyear <= maxyear' failed ** Message: could not grab keyboard Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x28007ce (Passphrase) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed Tested with Ubuntu 9.10 (seahorse 2.28.1) and with Ubuntu 10.04 alpha (seahorse 2.29.30)
Does it really never stop, or does it just take much longer than expected?
Adam, with the version 2.28.1 I have waited for for above an hour before killing the app. With the version 2.29.30 I'm waiting for above 20 minutes (I haven't killed seahorse yet).
I noticed in the launchpad bug at least the confirmation was on a 64-bit system. Is this the case with all reporters?
Adam, my tests were made on x86. P.S. I have just closed seahorse 2.29.30 after waiting for above 3 hours for PGP keys generation
Confirmed on seahorse 2.29.91 in Ubuntu 10.04 (development branch)
So, it looks only reproducible in Ubuntu 10.04, isn't it? I don't have this problem with 9.10
No Pablo, even in 9.10 I have this problem as you can see in the comment of the report. I have tested again the issue, this morning, on a fully updated 9.10 (x86_64) and yesterday on a fully updated 10.04 (x86) 20100224 development branch.
Adam, do you have any idea where to start and try to reproduce it? (In reply to comment #7) > No Pablo, even in 9.10 I have this problem as you can see in the comment of the > report. > > I have tested again the issue, this morning, on a fully updated 9.10 (x86_64) > and yesterday on a fully updated 10.04 (x86) 20100224 development branch. Sorry, I did read the report too fast. Does it happen also with any other encryption type, or only with DSA/Elgamal? Default PGP keys in 2.29.91 is RSA 2048.
Do you have installed gnupg, gnupg2 or both?
Setting as New because another ubuntu user has confirmed.
Pablo, I'm baffled by these reports because I'm currently developing on Ubuntu 9.10 and can generate a gpg key. I will admit it took a while to gen the 2048 RSA keypair, but it finished and a new key was displayed on the my personal keys tab. I have seahorse TRUNK gpg 1.4.9 gpgme 1.1.8
Hi I tested it in a virtual machine with the newest ubuntu (10.4), Seahorse 2.29.91 Default: RSA, 2048 created a key and DSA & Elgamal 768 was also successful It took some time to create the keys (several minutes), but I did not use the computer and the entropy pool was very likely quite empty. Hope this helps
Does generating a key on the command-line with `gpg --gen-key` work when Seahorse doesn't?
Bug 614576 might be the reason of this bug.
@Pablo, I think you are right. Anyway on seahorse 2.30 (the version included on Ubuntu 10.04 beta2, fully updated) the issue seems to be disappeared (even if the gpg key creation takes many minutes).
So can anybody still reproduce this in GNOME 2.30?
Closing as this works for me on 2.30 as well and Marco.