** 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
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
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
@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
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
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
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
Desktop Bugs, which is a bug assignee.
--
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.
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
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
Desktop Bugs, which is a bug assignee.
--
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
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
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
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
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
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
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
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
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
Desktop Bugs, which is a bug assignee.
--
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
Desktop Bugs, which
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
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)
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
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
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
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
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
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
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.
25 matches
Mail list logo
