After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728032 - Can't generate new GPG key
Can't generate new GPG key
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
3.8.x
Other Linux
: Normal major
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2014-04-11 11:48 UTC by Gabor Toth
Modified: 2018-08-03 19:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gabor Toth 2014-04-11 11:48:37 UTC
I have attempted to generate a new pair of PGP keys with Seahorse (Passwords and Keys).  It goes through till I set what I want - RSA key, set the strength (tried the default and later also changed to stronger - no difference in the bug behavior) put in full name and e-mail address and then asked for password and to confirm it.
  I did all that and the window came up "Generating Key" informing me that if I do a lot of actions such as mouse movements and so on then I help to generate the random data.  The bar goes back and forth indicating the process is working.
  After a while, in some minutes later another window pops up with the message:

  "Couldn't generate PGP key, General error"

  Leaves only on option "Close"  No key gets generated.

  I am using Ubuntu 13.10 on a Dell Inspiron 17R system with 8 GB ram.  All packages are up to date.  No other system errors currently (there was something with wine porfolio package not updating, but I have fixed that yesterday - I wouldn't think that it would be related anyway.)

I have then tried from command line and got the following:

"Not enough random bytes available.  Please do some other work to give
the OS a chance to collect more entropy! (Need 228 more bytes)"

I got this a number of times with different number of bytes still needed.  Not sure what is the point of displaying it but anyhow.  That is not a bug I guess.

However then came up the actual bug:

"gpg: no writable public keyring found: eof
Key generation failed: eof"


This is the message I get and no key is generated.  I suppose this is the same bug.

Please let me know if there is any other data needed.

  Seahorse version: 3.8.2

  Other than this error Seahorse seems to work all right and is keeping
  my passwords, can add new ones manually and generally seems to perform
  all right - besides the above bug.

  The bug can be reproduced every time on my system.  Tried it 3 times
  with the same result.

  Let me know if I should upload any extra log files.  I can help on the
  rest of the bug process too if needed (can not program, but can test
  or do other such things).

  I have already reported this bug from UBUNTU and it is filed in launchpad under Bug #1304888 on this link: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1304888

  Cheers,

  Gabor
Comment 1 André Klapper 2014-04-11 21:40:59 UTC
Out of curiosity, does it work when using "gpg --gen-key" on a shell?
Comment 2 Gabor Toth 2014-04-12 19:45:41 UTC
Did already see bug report above.

==>>I have then tried from command line and got the following:

"Not enough random bytes available.  Please do some other work to give
the OS a chance to collect more entropy! (Need 228 more bytes)"

I got this a number of times with different number of bytes still needed.  Not
sure what is the point of displaying it but anyhow.  That is not a bug I guess.

However then came up the actual bug:

"gpg: no writable public keyring found: eof
Key generation failed: eof"<<==
Comment 3 André Klapper 2014-04-12 20:47:55 UTC
So there seems to be no problem with Seahorse (which just calls gpg), but with gpg itself already?
Comment 4 GNOME Infrastructure Team 2018-08-03 19:38:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/103.