GNOME Bugzilla – Bug 325663
Seahorse fails to generate key
Last modified: 2006-01-09 02:45:28 UTC
Please describe the problem: Seahorse is unable to generate a new key using the Key Generation Assistant. Steps to reproduce: 1. Click the New button on the main window 2. Follow the instructions in the wizard and finally click Apply Actual results: Error message pops up: "Couldn't generate key General error" Expected results: Does this happen every time? Yes Other information: Tested on Ubuntu Dapper (6.04 development repository)
I just checked and didn't find a "New" button on the "main" window. Could you please submit a screen shot with the button in question circled?
Scratch that above comment, I'm jet lagged. I just created a key sucessfully with 0.8 on my slackware system. What versions of gpg and gpgme are you using? I'm using 1.4.2 and 1.0.3 respectively. Does this problem also occur in Ubuntu stable?
gnupg is reported as version 1.4.2-2ubuntu2. I don't have any packages named gpg or gpgme. I don't know if it occurs in Ubuntu stable, sorry. If I find the time, I might install the stable release and test.
Created attachment 56761 [details] The error message This is how the error message looks like when trying to generate the key.
I just tested this with a vanilla Ubuntu Breezy (stable) install with the latest security updates and it doesn't work there either. The same error message is shown. seahorse version 0.8-0ubuntu1 liggpgme11 version 1.0.2-1build1 gnupg version 1.4.1-1ubuntu1
I found the reason for this bug: seahorse-agent isn't running! I started seahorse-agent from a terminal and then started seahorse, and I'm able to generate a key now. I don't know who is responsible for it, but the agent should be running at all times, right? If not, seahorse itself should start it if it isn't running, instead of displaying "General error".
It still doesn't work under Ubuntu Dapper 6.04 (development), even after you start seahorse-agent, so the above solution only applies to Ubuntu Breezy 5.10 (stable).
New package version in the repositories. The bug appears to be fixed! libgpgme11 1.1.0-1 gnupg 1.4.2-2ubuntu2 seahorse 0.8.0-1ubuntu1 And you no longer have to have seahorse-agent running, the keys will be generated anyway. Suggesting marking this bug as FIXED, although it would be reassuring to hear from the developers if you actually changed something in the code, or if this was because of build problems caused by the Ubuntu .deb packages?
I think it was a build problem as it doesn't appear there have been any changes in our 0.8.x branch in 2 months. http://cvs.gnome.org/viewcvs/seahorse/?only_with_tag=seahorse-0-8 Thanks for staying on top of this Dave.