#!/bin/sh
envfile="${HOME}/.gnupg/gpg-agent.env"
if test -f "$envfile" && kill -0 $(grep GPG_AGENT_INFO "$envfile" | cut -d: -f 2) 2>/dev/null; then
eval "$(cat "$envfile")"
else
eval "$(gpg-agent --daemon --write-env-file "$envfile")"
fi
export GPG_AGENT_INFO
- set path in enigmail
/usr/bin/gpg2
- relogin
]]>ps aux | grep -v grep | grep gpg
in the list of processes when TB starts correctly.
]]>For me the problem seem to be gone now after my last update when Thunderbird 13.0 needed an update of enigmail.
Thought so too, but I still have the problem with TB 13 und Enigmail 1.4.2. Every now and then it works, but most of the time Enigmail fails to find and initialize gpg.
]]>I think my problem is also related to engmail.
When I close Thunderbird, it tends to remain running in the background. I have to kill the process, before I can restart Thunderbird.
It happens in about 50% of cases.I noticed that this problem occurs always when the OpenPGP-->Key_Management option cannot display the keys, trying to import them. At the same time the OpenPGP-->Settings option displays a statement "Unable to locate GnuPG" in the Files and Directories/Folders section. In all other cases Thunderbird can be closed normally. (I use Polish interface so the correct English names of the options may be different from the ones write here.)
I tried setting the location of GnuPG manually in the settings (/usr/bin/gnupg or /usr/bin/gnupg2), but that did not change the situation - Thunderbird cannot locate gnupg(2) in 50% cases. It looks rather funny to see to statements in the settings panel: one informing that gpg cannot be found and the other showing the location.
On top of that I have received a message signed with a separated signature. Enigmail says the signature is wrong, but when I save the signature file and run gnupg --verify, the signature is confirmed as correct. This seems to happen independently of the key management problem described above.
Yup, second that.
]]>I think my problem is also related to engmail.
When I close Thunderbird, it tends to remain running in the background. I have to kill the process, before I can restart Thunderbird.
It happens in about 50% of cases.
Same here. I don't even know where to start on this one, though. Sometimes, Enigmail initializes perfectly, automatically finds gpg2 and works. Sometimes, it doesn't find anything, hangs on trying to load the keys and then thunderbird-bin doesn't quit correctly.
Any recommendations?
]]>I think my problem is also related to engmail.
When I close Thunderbird, it tends to remain running in the background. I have to kill the process, before I can restart Thunderbird.
It happens in about 50% of cases.
I have that problem too.
]]>I noticed that this problem occurs always when the OpenPGP-->Key_Management option cannot display the keys, trying to import them. At the same time the OpenPGP-->Settings option displays a statement "Unable to locate GnuPG" in the Files and Directories/Folders section. In all other cases Thunderbird can be closed normally. (I use Polish interface so the correct English names of the options may be different from the ones write here.)
I tried setting the location of GnuPG manually in the settings (/usr/bin/gnupg or /usr/bin/gnupg2), but that did not change the situation - Thunderbird cannot locate gnupg(2) in 50% cases. It looks rather funny to see to statements in the settings panel: one informing that gpg cannot be found and the other showing the location.
On top of that I have received a message signed with a separated signature. Enigmail says the signature is wrong, but when I save the signature file and run gnupg --verify, the signature is confirmed as correct. This seems to happen independently of the key management problem described above.
How do you set your NSPR_LOG_MODULES variable to get your logs?
Do you have any problems with closing Thunderbird?
That's what I can find in the Enigmail logs:
[snip]
[DEBUG] enigmail.js: detectGpgAgent: gpg-connect-agent is executable
[CONSOLE] enigmail> /usr/bin/gpg-connect-agent
[ERROR] subprocess.jsm: got error from stdinWorker: expected type int, got (void 0)
[DEBUG] detectGpgAgent detection terminated with 256
[DEBUG] enigmail.js: detectGpgAgent: no running gpg-agent. Output='' error text='gpg-connect-agent: can't connect to the agent: IPC connect call failed'
[snip]
Anybody knows how to fix this? Couldn't find any bugs upstream (maybe just incapable of browsing super-slow bugzilla though).
]]>