Enigmail no longer works with Qubes split-gpg

102 views
Skip to first unread message

4315p2+7oq...@guerrillamail.com

unread,
Jul 13, 2016, 9:26:05 AM7/13/16
to qubes...@googlegroups.com
Hi,

Enigmail version 1.8.2 works flawlessly with qubes-gpg-client-wrapper, however from version 1.9 onwards this is not the case. Enigmail complains is no longer able to communicate with the gpg-agent:

"GnuPG reported an error in the communication with gpg-agent (a component of GnuPG).
This is a system setup or configuration error that prevents Enigmail from working properly and cannot be fixed automatically.
We strongly recommend that you consult our support web site at https://enigmail.net/faq"

Does anyone experienced the same issue? Don't want to use a older version of enigmail to solve this.
Has anyone solved this?

Thank you.

----
Sent using GuerrillaMail.com
Block or report abuse: https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D



Andrew David Wong

unread,
Jul 13, 2016, 11:19:14 AM7/13/16
to 4315p2+7oq...@guerrillamail.com, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-07-13 06:25, 4315p2+7oqw6t5msys3o via qubes-users wrote:
> Hi,
>
> Enigmail version 1.8.2 works flawlessly with qubes-gpg-client-wrapper,
> however from version 1.9 onwards this is not the case. Enigmail complains
> is no longer able to communicate with the gpg-agent:
>
> "GnuPG reported an error in the communication with gpg-agent (a component
> of GnuPG). This is a system setup or configuration error that prevents
> Enigmail from working properly and cannot be fixed automatically. We
> strongly recommend that you consult our support web site at
> https://enigmail.net/faq"
>
> Does anyone experienced the same issue? Don't want to use a older version
> of enigmail to solve this. Has anyone solved this?
>
> Thank you.
>

I'm using Enigmail 1.9.3 with Split GPG, and it's working fine. Do you have
all the latest updates in dom0 and your TemplateVM?

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXhlvoAAoJENtN07w5UDAwkwEQAJulkjfPQ5Vn7CukgcwENqKW
CqAjY+HPyZw3ww/OVoj7hAwZmY2Kp/vZ/1BNjJoy1aY1U45ScANXJ90IgVxwuAbu
T7ikpwUfHmJvIRjsO+wB8kSaxh+Ug3BfDfytpbpNs0mNYqUwpy4n0dUIcU5M0Eo4
zQCClZKPIhColmlJA4vkVkoaoEvDM1XbdHMMHkdrpIL4RTnsyLk2nyEjFN0dF24a
gujnX5raDggELtM8GasiOCayOSuIJNcTddYthh4unCWz8yKjrfyJjRpe0bI+O92Z
VFVTb1YroK8FJv397zBoyhFiPmsPavYqoTEnv4sFmSpXkPAVEr6PQGgbCtrxtqyT
JHw025HP8X50cvzTWlT19u7X0ap60GQzj5QbNZHAGiYCM3cI/ZKgwvqatWVXinNs
zuxszwf5IJgSv2ZpC04UWHp9Gfn6T90vLbDM3yvs+l9lPvKLPFOy39EQVvbZfvtk
igCIrYUvH+3JyilukFl1khkeR52iwyi1W49p7rNEKVsQFs9FdpEHskXbdC4e+Q8d
/A2Sqgr83X24YZgv1dDpshN+IRbTbeK2z6eLSRvwGYQF3ahcRROHctEu9mgQp1H9
ch/Xp99drUWelaiITaH8uTmwmDB7q31eP87qBUj9fh5UqxiRX8krUhS9lVem3rG3
TX9eRwLC+1jPjFCYgDha
=gg/U
-----END PGP SIGNATURE-----

431mo6+f16...@guerrillamail.com

unread,
Jul 13, 2016, 11:58:38 AM7/13/16
to qubes...@googlegroups.com
The signatures check does work but not the message encryption or signature.
I'm using Qubes 3.2Rc1 and using Debian 8 as the template and I have all the dom0 and template updates up to date.
Apparently it seems that the gnome-keyring is hijacking the gpg agent:


gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent.
gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system!
[GNUPG:] ERROR check_hijacking 33554509

431tz8+8ij...@guerrillamail.com

unread,
Jul 13, 2016, 1:02:33 PM7/13/16
to qubes...@googlegroups.com
Forgot to paste these entries:

[DEBUG] errorHandling.jsm: parseErrorOutputWith: return with c.errorMsg = gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent.


gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system!

[DEBUG] execution.jsm: EnigmailExecution.fixExitCode: agentType: gpg exitCode: 0 statusFlags 4194304
[DEBUG] encryption.jsm: encryptMessageEnd: command execution exit code: 1
[ERROR] mimeEncrypt.js: caught exception: undefined
Message: 'undefined'
File: undefined
Line: undefined
Stack: undefined

Apparently there are more users complaining about the same problem issue:

https://groups.google.com/forum/?nomobile=true#!msg/qubes-users/DQUzJ39H9Cc/Arm1sU3gBQAJ

Andrew David Wong

unread,
Jul 13, 2016, 2:45:27 PM7/13/16
to 431tz8+8ij...@guerrillamail.com, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-07-13 10:02, 431tz8+8ija10yovb66g via qubes-users wrote:
> Forgot to paste these entries:
>
> [DEBUG] errorHandling.jsm: parseErrorOutputWith: return with c.errorMsg =
> gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg:
> WARNING: GnuPG will not work properly - please configure that tool to not
> interfere with the GnuPG system! [DEBUG] execution.jsm:
> EnigmailExecution.fixExitCode: agentType: gpg exitCode: 0 statusFlags
> 4194304 [DEBUG] encryption.jsm: encryptMessageEnd: command execution exit
> code: 1 [ERROR] mimeEncrypt.js: caught exception: undefined Message:
> 'undefined' File: undefined Line: undefined Stack: undefined
>
> Apparently there are more users complaining about the same problem issue:
>
> https://groups.google.com/forum/?nomobile=true#!msg/qubes-users/DQUzJ39H9Cc/Ar
m1sU3gBQAJ
>
>
>
Issue opened:

https://github.com/QubesOS/qubes-issues/issues/2170

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXhow/AAoJENtN07w5UDAw8bMQALj8KVkZEeJCTDjfNmoXNeff
XvrhDcaF2/YN+Iinw3zrKplvi4ub/W98GxfT5t9cugFe67AJJdkKTmdtuaOMTCyh
evb+qp6CMLf9rSD2/ESQkcFlfeO6+N8WxuL4RR4zRh5T7yr2SOgwu6OBNAf4xJJY
nn5zliR80DKDnL2dNxJnKqdAVjozn2mxsH/0WCpxy9YhPXymZTtd/ma8Ew8vCOn7
iOzjgqvt85KtAsPa5j6OLfmNW3/I2n6JRXIw7pJkAp6ypiQsYCnTBqY31Gvua5NV
hMiSA4BMBiG1pvgRSDrf+BImwTAvowbGf5tpJO8WdPnxGE+1sE3Ovplw4AdceNQZ
E+lJInBT+UCseJt2nG5CnWD2W7Lg8zVxtkSrVg5WzqgHRdIoPi0GV8IteQcrxK+R
sQhvnbWrr0jrhWPpxZxcMv4Ua2ciw+Li7BxPlL5CkhoiWh4E6VPBq9Y4+f7kr0H3
YMS+b0+zWKwjCgNB+Kn98/ofEXiozmlf4FqjnChjZu6/q2PVxZzEl6wcetisMdWp
pfYhVIeCtQO+r1mloyXuFkr2vCrNFFRd3g5ncUecwTdnvmUyEDMJATvDAKK5+hk8
62ZLQkTxdvEXDll3PFt8ALkOs/UXel3x7p09ENRzPjw1uPfTl2XIM33hIvPDYRU4
2pSwgXnBOAAcV/IJ4MBf
=GjKw
-----END PGP SIGNATURE-----

Reply all
Reply to author
Forward
0 new messages