Confirmed on Ubuntu 14.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/321287
Title:
Seahorse won't generate a key when .gnupg directory owned by root,
only gives unhelpful "General
vishaltelangre upper workaround at #31 worked for me (Ubuntu 12.04.2
x86_64)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/321287
Title:
Seahorse won't generate a key when .gnupg directory owned
On Ubuntu 12.04, I was having same issue. By changing group and owner of
`.gnupg/*` resolved this issue for me:
vishal@vishal:~$ ls -la | grep .gnupg
drwx-- 2 root root 4096 Apr 23 18:12 .gnupg
vishal@vishal:~$ sudo chown -R vishal .gnupg
vishal@vishal:~$ sudo chgrp -R vishal .gnupg
the workaround is giving permission to your user:
sudo chown; chgrp user file (without the quotation)
you have to do this to all files inside the ~/.gnupg directory
and then you can create your key!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Description changed:
+ nUboon2Age's recharacterization of bug: When the ~/.gnupg/ directory and
+ its contents are owned by root. To get Seahorse working again the
+ ~/.gnupg/ directory must be deleted. This allows Seahorse to run not
+ only new gpg creation but also run 'Sync and Publish
Hi nUboon2Age,
I see some problems with (2.1-2.3). The most critical point is: if we
delete the whole directory (or even some of the .gpg files) we are
potentially destroying user data -- gone are your private keys, your
trusted database, your list of locally-signed keys, etc. In my case, for
I think the comments by Jimbo and Dominic above are probably a different
bug (possibly bug #321287) which then would need to be written up
separately.
Note: looking at the gpg documentation, my guess is that
http://www.gnupg.org/gph/en/manual.html#AEN26 gives General error for
several different
C de-Avillez, yes that is a good point about potentially unintentionally
destroying other data. I wonder if Seahorse just changed the
permissions to be controlled by userid if that would solve the problem.
I think it probably would. The thing is that if you give new to
intermediate users with
New Suggested Fix (taking into account C de-Avillez's input above):
1) inform the operator that the ~/.gnupg/ directory and all the files in it are
owned by root and therefore cannot be used to generate a key.
2) either
(my strong preference)
2.1.1) give operator option to change the ownership
Unfortunately, if ~/.gnupg is owned by root, Seahorse will not be able
to chown it back:
cer...@xango2:~$ ls -l test
total 0
cer...@xango2:~$ chmod 700 test
cer...@xango2:~$ sudo chown root:root test
[sudo] password for cerdea:
cer...@xango2:~$ ls -la test
ls: cannot open directory test:
10 matches
Mail list logo
