[Bug 321287] Re: Seahorse will not generate a key
** Changed in: seahorse (Ubuntu) Status: Incomplete = New -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
Confirm this on Lucid 10.04 i686 Above is requested: please do a 'ls -l ~/.gnupg/*.gpg'. This will will list (among other things) which user and group owns the files. There should be 3 files, pubring.gpg, secring.gpg, and trustdb.gpg. These 3 files -- in fact, *all* under ~/.gnupg -- should be owned by your userid, your group, not by root, or any other user. Please comment on what you find. Thanks. Here is my finding: $ ls -l ~/.gnupg/*.gpg ls: cannot access /home/username/.gnupg/*.gpg: Permission denied username@computername:~$ sudo ls -l ~/.gnupg/*.gpg ls: cannot access /home/username/.gnupg/*.gpg: No such file or directory My steps were: first I tried to generate a PGP key from the command line but failed and was unable to find the steps to do it properly that way. So I installed Seahorse. 1) Started Seahorse from menu 2) Tried 'Sync and publish keys' but that seemed to stall, so I cancelled it. 3) I press on the 'new' button to generate a new key. I select PGP key and press continue. I fill out the fields for 'real name', 'email address', and 'comment'. I so NOT click on the arrow for advanced options. I click on 'Create'. It asks me for a Passphrase for New PGP Key. I enter my password two times, the same both times. I click OK. A box pops up with an error message in it: Couldn't generate PGP key General error -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
@nUboon2Age (and, actually, just for the record, since s/he did not subscribe to this bug... fire-and-forget type of thing) $ ls -l ~/.gnupg/*.gpg ls: cannot access /home/username/.gnupg/*.gpg: Permission denied The above is already good enough to state your userId does not seem to be the owner of the directory ~/.gnupg, or of the files under it. Either one or the other gave you a Permission denied error. You can find out byt running 'ls -la ~ | grep gnupg'. ** Changed in: seahorse (Ubuntu) Importance: Medium = Low ** Changed in: seahorse (Ubuntu) Status: New = Incomplete -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
Update and RESOLUTION: What it boils down to is that previously I'd run the command line gpg tool with sudo. Like the original gug reporter, my .gnupg directory was therefore owned by root. To fix it I deleted the directory and ran Seahorse again in normal user mode (ie. w/o sudo). Here's my investigative steps that lead me there: even though above I reported that ls -l and even sudo ls -l didn't see the file, when I check it with sudo nautilus (view hidden files) it does see the .gnupg directory and the directory and files are owned by root. Since the date on the files is yesterday I'm guessing that they were created by my command line attempts yesterday and since they are owned by root I'm guessing I did 'sudo' to create a PGP key pair after an attempt to create it without sudo failed with an error. The files are: gpg.conf pubring.gpg pubring.gpg~ trustdb.gpg I deleted the entire directory and try again from Seahorse without sudo priviledges. WORKED! ** Changed in: seahorse (Ubuntu) Status: Incomplete = Confirmed -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
Suggested Fix: 1) inform the operator that the .gnupg directory is owned by root and therefore cannot be used to generate a key 2) either (preferred) a) give operator option to delete the directory b) authenticate their sudo password, delete the directory and then c) ask if they wish to try again (ie. without having to re-enter the configuration info). or (at least) b) provide a short explanation that they will need to do the steps above manually. Note: the op reported that the error dialog box actually showed the html tags. Since this is no longer the case, that aspect of the bug seems to have been fixed. ** Summary changed: - Seahorse will not generate a key + Seahorse won't generate a key when .gnupg directory owned by root, only gives unhelpful General error -- Seahorse won't generate a key when .gnupg directory owned by root, only gives unhelpful General error https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I can confirm this on Lucid 10.04 x64. Never expires option was checked; tried to generate a PGP key. -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I also have this issue on Ubuntu 9.10 AMD64. It occurs here each time. Seahorse - File - New - PGP Key. I fill in everything and keep the default options. Then I have to wait for several minutes while a popup windows key generation / primegen is displayed. Then I get the General error message. I still have the ownership over pubring.gpg, and never used gksudo to launch Seahorse. What may I do to help investigate this bug ? Cheers ! -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
OK so, I figured out more or less what was wrong. The first time I created the PGP Key, I didn't specify a password (I wanted to check what would happen). It instantly displayed general error. Then, my subsequent tries triggered the issue that is specified above. When I tried to create the key via the terminal (as it didn't work with seahorse), here is what was displayed at the end of the process : gpg: fatal: /home/sandra/.gnupg/trustdb.gpg: base de confiance invalide Actually, some bad data had been stored the first time even though the process had failed. I had deleted by hand pubring.gpg because I had noticed some data had been stored there, but I should have deleted the entire directory as well. Anyway, there's a bug somewhere. Any idea where I should report it ? -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I got this error but I was able to resolve it by changing the ownership of pubring.gpg from root to me. -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
Thanks for reporting, still can't reproduce this on current karmic. Could you give detailed steps or maybe record a screencast on how to reproduce this problem? ** Changed in: seahorse (Ubuntu) Status: New = Incomplete -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I can confirm this problem, as mentioned in detail by Jimbo (https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/321287/comments/11) System: gpg (GnuPG) 1.4.9 2.6.27-14-generic #1 SMP Tue Jun 30 19:57:39 UTC 2009 i686 GNU/Linux * The error occurs only if you click the button _Create (with the mouse). If you press Alt+C or focus this button and press Enter, the key will be generated as normal (with expiration date 1970-01-01). * Only the command line message ** (seahorse:26768): CRITICAL **: egg_datetime_get_as_time_t: assertion `EGG_IS_DATETIME (edt)' failed ** Message: could not grab keyboard seems to be interesting, because the other ones appears even if you don't uncheck Never Expires. * There's no date-time-field left to the Never expires-button as seen here: http://media.ubuntuusers.de/wiki/attachments/34/28/seahorse-new- pgp-key.png * Surprisingly, after appearence of the error message bigbCouldn't generate PGP key/b/big, the sorting order first PGP-key, second SSH, has changed in SSH, PGP (at Generate a new key-window). ** * Another bug maybe connected with this one: at key properties-window details: changing the expiration date at a date less or equal the current date will result in the message: - bigbCouldn't change expiry date/b/big General error Command line messages, first before closing the error message window --- ** (seahorse:29571): CRITICAL **: file seahorse-pgp-key-op.c: line 1024 (edit_expire_transit): should not be reached --- and after closing --- (seahorse:29571): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed --- -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
Importance for me is actually _High_ ** Description changed: Binary package hint: seahorse Seahorse will not generate a new key. I have used gksudo to launch seahorse from the command line. Seahorse opens. I press on the 'new' button to generate a new key. I select PGP key and press continue. I fill out the fields for 'real name', 'email address', and 'comment'. I click on the arrow for advanced options. I select 4096 for key strength. I remove the check from the box that says never expires. I click on 'Create'. It asks me for a Passphrase for New PGP Key. I enter my password two times, the same both times. I click oK. A box pops up with an error message in it: bigbCouldn't generate PGP key/b/big General error The html tags are in the actual error message. No key is generated. I am running Ubuntu 8.10 gpg is installed: e...@leibniz:~$ gpg --version gpg (GnuPG) 1.4.9 e...@leibniz:~$ uname -a Linux leibniz 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux + + === + + I too have the similar problem: + right click on folder, select Encrypt. At this point I get message that no key are available and seahorse opens up. + + I click on File, New, fill out name, email, comment, leave other + defaults alone. Next I get the password box I fill in the password, and + the working bar apears for about a minute or two and then I get an error + message saying that it can not generate key. + + I was running 8.10 with latest patches, last night I upgraded to 9.04 to + see if it would help, but it did not, still get the same error. + + Thanks for any one looking into this. -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
You also need to uncheck the never expires option to reproduce this. -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
Get a bigbCouldn't generate PGP key/b/big General error msg as well. ~/.gnupg owned by me. Command line did this. j...@gerrard:~$ seahorse ** Message: init gpgme version 1.1.6 (seahorse:6354): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (seahorse:6354): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (seahorse:6354): GLib-GObject-WARNING **: invalid cast from `GtkCheckButton' to `EggDateTime' ** (seahorse:6354): CRITICAL **: egg_datetime_get_as_time_t: assertion `EGG_IS_DATETIME (edt)' failed ** Message: could not grab keyboard ** Changed in: seahorse (Ubuntu) Status: Incomplete = New -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
on Ubuntu 8.10 -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
setting to Incomplete: waiting on reply. ** Changed in: seahorse (Ubuntu) Status: New = Incomplete -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I tried this again, this time on a fresh Jaunty install (that had no existing .gnupg directory) and could not reproduce the error. -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
Sorry, Mike, I did not comment before because I (wrongly) considered you had already seen your issue: at one point in time either you ran seahorse or gpg under sudo or gksudo. Your issue was somehow the ./gpg files got owned by root. This is different from Ithor. @Ithor: please: (1) make sure all files under your ~/.gnupg are still owned by your userid; (2) run seahorse from the command line; (3) try to repeat the issue; (4) post all messages generated here. Thank you. -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I ran across the same problem this morning and found the trustdb file was owned by root. -rw--- 1 root root 1200 2008-11-10 10:24 /home/mike/.gnupg/trustdb.gpg changing ownership: 1.) Allowed me to add new keys 2.) Made old ones visible that I didn't know were there. (forgotten long ago) -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I apologize, I am on Jaunty as well. -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I confirm that gpg key generation is broken on Ubuntu 8.10 running on Linux cesar 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux I get pretty the same error. Here's the info you asked: ce...@cesar:~$ ls -A .gnupg/ -ld drwx-- 2 cesar cesar 232 2009-03-10 16:13 .gnupg/ ce...@cesar:~$ ls -ld /home/cesar/.gnupg/ drwx-- 2 cesar cesar 232 2009-03-10 16:13 /home/cesar/.gnupg/ ce...@cesar:~$ ls -l /home/cesar/.gnupg/ Total 20 -rw--- 1 cesar cesar 28 2008-10-26 01:07 gpg.conf -rw--- 1 cesar cesar 2614 2008-12-11 00:58 pubring.gpg -rw--- 1 cesar cesar 2614 2008-12-11 00:58 pubring.gpg~ -rw--- 1 cesar cesar 600 2009-03-10 16:14 random_seed -rw--- 1 cesar cesar0 2008-10-26 02:23 secring.gpg -rw--- 1 cesar cesar 1200 2008-12-11 00:58 trustdb.gpg As you can see I'm the only user who has access to these files (as it should be, afaiu). ** Changed in: seahorse (Ubuntu) Status: Invalid = New -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again! ** Changed in: seahorse (Ubuntu) Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: Incomplete = Invalid -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I'm glad that you cannot reproduce it on Jaunty. I first tried to generate a new key without using gksudo and it resulted in the exact same message. -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
emeriste, please do a 'ls -l ~/.gnupg/*.gpg'. This will will list (among other things) which user and group owns the files. There should be 3 files, pubring.gpg, secring.gpg, and trustdb.gpg. These 3 files -- in fact, *all* under ~/.gnupg -- should be owned by your userid, your group, not by root, or any other user. Please comment on what you find. Thanks. -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321287] Re: Seahorse will not generate a key
I cannot reproduce this on Jaunty. This is, nevertheless, a dangerous thing to do: if you are logged under your own userid (not root), and you 'gksudo seahorse', you will change the ownership of the ./gnupg/(pub|sec)ring.gpg to root -- which will mean you will lose access to your gpg keyrings. On the other hand, this message is weird... ** Changed in: seahorse (Ubuntu) Importance: Undecided = Medium Status: New = Incomplete -- Seahorse will not generate a key https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
