>From the Enigmail log:

2015-07-20 13:08:59.778 [CONSOLE] enigmail> /usr/bin/gpg2 --charset
utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2
--fixed-list-mode --with-colons --list-keys
2015-07-20 13:08:59.797 [DEBUG]   enigmail> DONE
2015-07-20 13:08:59.797 [DEBUG] enigmail.js: Enigmail.execCmd: exitCode = 2
2015-07-20 13:08:59.797 [DEBUG] enigmail.js: Enigmail.execCmd: errOutput
= gpg: error reading key: Invalid user ID

2015-07-20 13:08:59.797 [DEBUG] enigmailCommon.jsm: parseErrorOutput:
status message:
gpg: error reading key: Invalid user ID

2015-07-20 13:08:59.797 [DEBUG] enigmailCommon.jsm: parseErrorOutput:
statusFlags = 00000000
2015-07-20 13:08:59.797 [DEBUG] enigmailCommon.jsm: parseErrorOutput():
return with errorMsg = gpg: error reading key: Invalid user ID
2015-07-20 13:08:59.797 [CONSOLE] gpg: error reading key: Invalid user ID



When I run that exact same command line myself, here's what I get:

[rjh@localhost ~]$ /usr/bin/gpg2 --charset utf-8 --display-charset utf-8
--batch --no-tty --status-fd 2 --fixed-list-mode --with-colons --list-keys
[GNUPG:] KEYEXPIRED 1355698800
[GNUPG:] KEYEXPIRED 1355698800
[GNUPG:] KEYEXPIRED 1355698800
[GNUPG:] KEYEXPIRED 1355698800
[GNUPG:] KEYEXPIRED 1355698800
[GNUPG:] KEYEXPIRED 1355698800
[GNUPG:] KEYEXPIRED 1355698800
tru::1:1437411957:1453409426:3:1:5
pub:r:2048:1:B700F482FEAF8109:1109070193:::-:::sc::::::
rvk:::17::::::7B279258D06B6AA89A48EA9C4E8FF9863D7489C0:80:
uid:r::::1222156786::39B1321959FFCED2E80E40B4405D136721BD8276::Robert J.
Hansen:
uid:r::::1222156791::4AB5F9CF297E803F6DCD857CD66992EA53A388A3::Robert J.
Hansen <[email protected]>:
...
... [a whole lot of keydump omitted]
...

Nowhere am I receiving an error about an error reading a key, or an
invalid user ID.

Can anyone shed some light on what's happening?

_______________________________________________
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

Reply via email to