Hi Seth,

I have tried that and this is what I got:

"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.


Best,


Gabor Toth

Phone: +45-2163-4983
Skype: gabor.me

Copenhagen, Denmark


On Wed, Apr 9, 2014 at 8:21 PM, Seth Arnold <email address hidden>wrote:

> As a workaround, you can probably use gpg --gen-key to generate a key.
> If there is an error, it may be more informative than seahorse's
> wrapper.
>
> Thanks
>
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1304888
>
> Title:
>   Cannot generate new PGP key
>
> Status in "seahorse" package in Ubuntu:
>   New
>
> Bug description:
>   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.)
>   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).
>
>   Marked it as security vulnerability since effects a security program,
>   also I need a PGP key for secure work and can't make one.
>
>   Cheers,
>
>   Gabor
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 13.10
>   Package: seahorse 3.8.2-0ubuntu1
>   ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
>   Uname: Linux 3.11.0-19-generic x86_64
>   ApportVersion: 2.12.5-0ubuntu2.2
>   Architecture: amd64
>   Date: Wed Apr  9 09:57:15 2014
>   EcryptfsInUse: Yes
>   ExecutablePath: /usr/bin/seahorse
>   InstallationDate: Installed on 2013-09-14 (206 days ago)
>   InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64
> (20130424)
>   MarkForUpload: True
>   SourcePackage: seahorse
>   UpgradeStatus: Upgraded to saucy on 2013-10-19 (171 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1304888/+subscriptions
>