I've experienced the same behaviour in Jaunty. Running the underlying gpg command from the terminal, I saw the error:
gpg: no writable public keyring found: eof Key generation failed: eof A listing of ~/.gnupg shows: -rw------- 1 andrew andrew 9508 2009-04-25 10:06 gpg.conf -rw------- 1 root root 0 2009-06-14 15:42 pubring.gpg -rw------- 1 andrew andrew 600 2009-08-27 10:34 random_seed -rw------- 1 andrew andrew 0 2009-08-27 10:19 secring.gpg -rw------- 1 andrew andrew 40 2009-08-27 10:19 trustdb.gpg so pubring.gpg has somehow become owned by root. Changing this permission back to the owning user fixes the issue in Seahorse. I then created a fresh test user, logged in as the user, and was able to generate a pgp key using seahorse just fine. So I'm suspecting that "something else" has clobbered the directory permissions at some point. It's worth noting that the suggestion to run seahorse as root will 'fix' this issue, but in the long run will make life worse, as it'll probably further screw up the .gnupg permissions. Much better to fix the file ownership as above. -- [Intrepid] Unable to encrypt a folder https://bugs.launchpad.net/bugs/297206 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
