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 614576 - Hangs generating PGP, if the computer does not have enough entropy
Hangs generating PGP, if the computer does not have enough entropy
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
2.29.x
Other Linux
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2010-04-01 12:29 UTC by Angel Abad
Modified: 2018-08-03 19:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Angel Abad 2010-04-01 12:29:37 UTC 
In Ubuntu Lucid Ara Pulido reported:

Steps to reproduce:

* Create a new clean virtual machine with Lucid
* Try to generate a PGP key using gpg --gen-key. You will receive the following error:

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

* But, if you try to do the same with Seahorse, instead of showing the error to the users, it just hangs with the dialog "Generating key"

Launchpad ref: https://bugs.edge.launchpad.net/ubuntu/+source/seahorse/+bug/552616

Thanks!
Comment 1 Pablo Castellano (IRC: pablog) 2010-04-01 17:37:26 UTC 
This could be the reason for bug 606268
Comment 2 Marco Pallotta 2010-04-18 22:33:56 UTC 
@Pablo, as you can read on bug 606268 the seahorse issue disappeared on seahorse 2.30 (the one included on Ubuntu 10.04 beta2, fully updated) even if the message on this bug report (Not enough random bytes available) is still present if you create the key through cli using gpg --gen-key.
Comment 3 GNOME Infrastructure Team 2018-08-03 19:17:54 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/45.