[Solved] Seahorse and GPG

[petedan10]

When trying to import a keyring, the keys are recognized and listed correctly, but pressing Import shows

Code: Select all

Import failed: Failed to execute child process "gpg" (No such file or directory)

gpg works fine from the command line, but adding keys using the command line doesn't result in them showing up in Seahorse.

Is this a general problem or something is misconfigured on my side?


(Edit: I thought I also wasn't able to create a new key but I was wrong)

[doktor5000]

but adding keys using the command line doesn't result in them showing up in Seahorse.

Can you post an example command you tried, including the output?

[petedan10]

I would import an existing keyring containing only public keys using

Code: Select all

gpg --import mykeyring

and the keys were imported and could be used perfectly from the command line (I have since deleted the specific installation so I can't provide the output, but everything worked fine from the command line).

In the meantime, I tried a test using gpa and seahorse at the same time to see what happens. Using seahorse, I couldn't import an existing keyring, but using gpa the keyring was imported (into gpa) correctly.

However, gpa would give me a "key not valid" message when trying to verify a file with a known good signature and a correctly imported key.

I wonder if someone else has tried those functions and found them working properly or this could be a bug.

[petedan10]

It looks like many people on many distributions have problems with Seahorse and that it suffers from various bugs.

While waiting for future versions here is what I found to be the best solution:

1. To import an existing keyring, use the terminal:

Code: Select all

gpg --import mykeyring.asc

Then in Seahorse check "Show any" under View menu

(if this doesn't work, try gpg2 instead of gpg)

2. To verify signatures using a GUI and right click, you have to install first Nautilus and then the Seahorse Nautilus extension.

I believe some custom editing with caja-actions will provide similar functionality with Caja, but I haven't worked on that yet.