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.
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!