On Tue 2015-01-20 15:49:16 -0500, Jogi Hofmüller wrote:
> /usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --batch --no-tty
> --status-fd 2 --with-fingerprint --fixed-list-mode --with-colons --list-keys
>
> Actually the error also occurs on the command line but it's not
> visible.
Sorry, i don't know what this means. how do you know about the error
from the commandline if it is not visible? Which error are you
referring to?
> As LeRoy pointed out, using gpg instead of gpg2 is a viable solution
> for now. The above command line works without error when using gpg
> instead of gpg2.
Hm, it would be good to track down what the problem is with gpg2, though
(enigmail should work with either gpg or gpg2), and i still don't feel i
have enough to reproduce the problem yet.
If posting a full transcript [0] to the mailing list is not ok for you,
i'd be happy to receive a redacted transcript via private mail of the
errors you're describing if you think that might help to track down the
problem.
--dkg
[0] https://support.mayfirst.org/wiki/terminal_transcripts
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
