Seahorse corrupts trustdb.gpg databse when no password is given while creating an openGPG key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
seahorse (Ubuntu) |
Incomplete
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: seahorse
Ubuntu 9.10, AMD64.
Well, this bug is quite easy to trigger.
Seahorse -> File -> New -> GPG Key
when a password is asked, don't choose any, just validate (it is accepted by seahorse as both (empty) passwords are the same :)
Then a popup window "key generation / primegen" is displayed for a very short time,
then the error windows is displayed : "general error".
OK, so far it's not an issue because it wasn't supposed to work.
BUT THEN all subsequent attempts to create a GPG key will fail. After "key generation / primegen" is displayed for several minutes, you also get "general error".
When I tried to create a key via the terminal I obtained :
gpg: fatal: /home/sandra/
So I figured out that the .gnupg files were corrupted by my first attempt to create a key while not providing any password. Indeed, there were even some data in "pubring.gpg" with my name in it, that had been added during my failed attempts.
Anyway, after deleting .gnupg, everything worked as expected. I still think, though, that this behaviour is a bug :)
Cheers, thanks for reading ;)
Changed in seahorse (Ubuntu): | |
status: | Incomplete → New |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.