| 1 |
On Thu, Feb 25, 2010 at 07:01:12AM +0000, Mick wrote: |
| 2 |
> 2010-02-25 06:48:32 gpg-agent[6741] starting a new PIN Entry |
| 3 |
> gpg-agent[6741]: can't connect server: `ERR 67109133 can't exec |
| 4 |
> `/usr/bin/pinentry-qt': No such file or directory' |
| 5 |
> 2010-02-25 06:48:32 gpg-agent[6741] can't connect to the PIN entry module: IPC |
| 6 |
> connect call failed |
| 7 |
|
| 8 |
<snip> |
| 9 |
|
| 10 |
> Why is it trying to call /usr/bin/pinentry-qt?! |
| 11 |
> |
| 12 |
> `ERR 67109133 can't exec `/usr/bin/pinentry-qt' |
| 13 |
> |
| 14 |
> Is this a valid binary these days, or an older qt3 version? I think it should |
| 15 |
> be /usr/bin/pinentry: |
| 16 |
> |
| 17 |
> $ ls -la /usr/bin/pinentry |
| 18 |
> lrwxrwxrwx 1 root root 12 Feb 24 07:01 /usr/bin/pinentry -> pinentry-qt4 |
| 19 |
|
| 20 |
Looks like you found your problem. I am not absolutely sure why |
| 21 |
pinentry-qt is the default now. The man page says that running |
| 22 |
'gpg-agent --version' will tell you what the default pinentry program |
| 23 |
it calls is, and that depends on installation. So maybe file a bug? I |
| 24 |
don't know whether this is a configuration/USE issue or something |
| 25 |
hardcoded in the distribution. |
| 26 |
|
| 27 |
In any case, two work-arounds are available: |
| 28 |
*) create a symlink of pinentry-qt to your actual pinentry binary. |
| 29 |
*) start gpg-agent with the '--pinentry-program' option. |
| 30 |
|
| 31 |
Cheers, |
| 32 |
|
| 33 |
W |
| 34 |
-- |
| 35 |
Willie W. Wong wwong@××××××××××××××.edu |
| 36 |
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire |
| 37 |
et vice versa ~~~ I. Newton |
Archives