[opensuse] Enigmail issues in Thunderbird on openSUSE LEap, anyone else?
Hi, Sometime earlier this week Enigmail started acting up: """ 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. """ I restarted gpg-agent /usr/bin/gpg-agent --sh --daemon --keep-display --write-env-file /home/rjschwei/.gnupg/agent.info-mountain:0 but that didn't do the trick. Also restarted Thunderbird, also to no avail :( -> rpm -qf /usr/bin/gpg-agent gpg2-2.0.24-5.1.x86_64 -> rpm -qf /usr/bin/thunderbird MozillaThunderbird-38.6.0-10.1.x86_64 Anyone else seeing issues with signing mail? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/16/2016 04:23 PM, Robert Schweikert wrote:
I restarted gpg-agent
/usr/bin/gpg-agent --sh --daemon --keep-display --write-env-file /home/rjschwei/.gnupg/agent.info-mountain:0
I'm not sure that would work. Normally, GPG_AGENT_INFO is an environment variable that is inherited from the desktop startup. You would have to fix that at the command line, and then start Thunderbird at that command line so it would get the updated environment value. The newer gpg in Tumbleweed puts the agent socked in $HOME/.gnupg, so that restarting probably works there. But that isn't in Leap 42.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/16/2016 09:35 PM, Neil Rickert wrote:
On 03/16/2016 04:23 PM, Robert Schweikert wrote:
I restarted gpg-agent
/usr/bin/gpg-agent --sh --daemon --keep-display --write-env-file /home/rjschwei/.gnupg/agent.info-mountain:0
I'm not sure that would work.
Normally, GPG_AGENT_INFO is an environment variable that is inherited from the desktop startup. You would have to fix that at the command line, and then start Thunderbird at that command line so it would get the updated environment value.
The newer gpg in Tumbleweed puts the agent socked in $HOME/.gnupg, so that restarting probably works there. But that isn't in Leap 42.1
Thus, I suppose the instructions here [1] are somewhat useless as when starting the debugging session on the agent Thunderbird would not find the agent to communicate with I suppose. I did try the debugging just in case but all that is produced is the following: handler 0x5573bdb32270 for fd 7 started gpg-agent[30224]: chan_7 -> OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 <- OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 -> GETINFO pid gpg-agent[30224]: chan_7 <- GETINFO pid gpg-agent[30224]: chan_7 -> D 30224 gpg-agent[30224]: chan_7 -> OK gpg-agent[30224]: chan_6 <- D 30224 gpg-agent[30224]: chan_6 <- OK gpg-agent[30224]: chan_6 -> BYE gpg-agent[30224]: chan_7 <- BYE gpg-agent[30224]: chan_7 -> OK closing connection gpg-agent[30224]: handler 0x5573bdb32270 for fd 7 terminated -> ps -A | grep 30224 30224 ? 00:00:00 gpg-agent Looks as if gpg-agent is talking to itself? Thus begs the question if I somehwo picked up an incompatibility between the gpg version that's on Leap adn Enigmail TB plugin? The Enigmail plugin is version 1.9.1 Help is appreciated. Thanks, Robert [1] https://enigmail.net/index.php/en/faq?view=category&id=14 -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mar 18, 2016, at 09:19, Robert Schweikert <rjschwei@suse.com> wrote:
On 03/16/2016 09:35 PM, Neil Rickert wrote:
On 03/16/2016 04:23 PM, Robert Schweikert wrote:
I restarted gpg-agent
/usr/bin/gpg-agent --sh --daemon --keep-display --write-env-file /home/rjschwei/.gnupg/agent.info-mountain:0
I'm not sure that would work.
Normally, GPG_AGENT_INFO is an environment variable that is inherited from the desktop startup. You would have to fix that at the command line, and then start Thunderbird at that command line so it would get the updated environment value.
The newer gpg in Tumbleweed puts the agent socked in $HOME/.gnupg, so that restarting probably works there. But that isn't in Leap 42.1
Thus, I suppose the instructions here [1] are somewhat useless as when starting the debugging session on the agent Thunderbird would not find the agent to communicate with I suppose.
I did try the debugging just in case but all that is produced is the following:
handler 0x5573bdb32270 for fd 7 started gpg-agent[30224]: chan_7 -> OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 <- OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 -> GETINFO pid gpg-agent[30224]: chan_7 <- GETINFO pid gpg-agent[30224]: chan_7 -> D 30224 gpg-agent[30224]: chan_7 -> OK gpg-agent[30224]: chan_6 <- D 30224 gpg-agent[30224]: chan_6 <- OK gpg-agent[30224]: chan_6 -> BYE gpg-agent[30224]: chan_7 <- BYE gpg-agent[30224]: chan_7 -> OK closing connection gpg-agent[30224]: handler 0x5573bdb32270 for fd 7 terminated
-> ps -A | grep 30224 30224 ? 00:00:00 gpg-agent
Looks as if gpg-agent is talking to itself?
Thus begs the question if I somehwo picked up an incompatibility between the gpg version that's on Leap adn Enigmail TB plugin?
The Enigmail plugin is version 1.9.1
Help is appreciated.
Which GUI are you using? I had problems with gnome as the gpg-agent and the wallet were conflicting. I got it to work with KDE, but I had to put the gpg-agent invocation in my .bcashrc, not .xinitrc. I wonder if what you are facing is something similar to what I faced with GNOME. Unfortunately, I did not take notes as to the exact problems with GNOME and how I got it to work with KDE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/18/2016 09:27 AM, Tom Kacvinsky wrote:
On Mar 18, 2016, at 09:19, Robert Schweikert <rjschwei@suse.com> wrote:
On 03/16/2016 09:35 PM, Neil Rickert wrote:
On 03/16/2016 04:23 PM, Robert Schweikert wrote:
I restarted gpg-agent
/usr/bin/gpg-agent --sh --daemon --keep-display --write-env-file /home/rjschwei/.gnupg/agent.info-mountain:0
I'm not sure that would work.
Normally, GPG_AGENT_INFO is an environment variable that is inherited from the desktop startup. You would have to fix that at the command line, and then start Thunderbird at that command line so it would get the updated environment value.
The newer gpg in Tumbleweed puts the agent socked in $HOME/.gnupg, so that restarting probably works there. But that isn't in Leap 42.1
Thus, I suppose the instructions here [1] are somewhat useless as when starting the debugging session on the agent Thunderbird would not find the agent to communicate with I suppose.
I did try the debugging just in case but all that is produced is the following:
handler 0x5573bdb32270 for fd 7 started gpg-agent[30224]: chan_7 -> OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 <- OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 -> GETINFO pid gpg-agent[30224]: chan_7 <- GETINFO pid gpg-agent[30224]: chan_7 -> D 30224 gpg-agent[30224]: chan_7 -> OK gpg-agent[30224]: chan_6 <- D 30224 gpg-agent[30224]: chan_6 <- OK gpg-agent[30224]: chan_6 -> BYE gpg-agent[30224]: chan_7 <- BYE gpg-agent[30224]: chan_7 -> OK closing connection gpg-agent[30224]: handler 0x5573bdb32270 for fd 7 terminated
-> ps -A | grep 30224 30224 ? 00:00:00 gpg-agent
Looks as if gpg-agent is talking to itself?
Thus begs the question if I somehwo picked up an incompatibility between the gpg version that's on Leap adn Enigmail TB plugin?
The Enigmail plugin is version 1.9.1
Help is appreciated.
Which GUI are you using?
Using XFCE
I had problems with gnome as the gpg-agent and the wallet were conflicting. I got it to work with KDE, but I had to put the gpg-agent invocation in my .bcashrc, not .xinitrc. I wonder if what you are facing is something similar to what I faced with GNOME. Unfortunately, I did not take notes as to the exact problems with GNOME and how I got it to work with KDE.
Well there are plenty of GNOME and XFCE users and one would suspect that the problem should not be unique especially sine the major components involved (gpg, TB) are from the "standard" repos. Unfortunately I do not recall what I did right before the problem started showing up. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/18/2016 09:19 AM, Robert Schweikert wrote:
On 03/16/2016 09:35 PM, Neil Rickert wrote:
On 03/16/2016 04:23 PM, Robert Schweikert wrote:
I restarted gpg-agent
/usr/bin/gpg-agent --sh --daemon --keep-display --write-env-file /home/rjschwei/.gnupg/agent.info-mountain:0
I'm not sure that would work.
Normally, GPG_AGENT_INFO is an environment variable that is inherited from the desktop startup. You would have to fix that at the command line, and then start Thunderbird at that command line so it would get the updated environment value.
The newer gpg in Tumbleweed puts the agent socked in $HOME/.gnupg, so that restarting probably works there. But that isn't in Leap 42.1
Thus, I suppose the instructions here [1] are somewhat useless as when starting the debugging session on the agent Thunderbird would not find the agent to communicate with I suppose.
I did try the debugging just in case but all that is produced is the following:
handler 0x5573bdb32270 for fd 7 started gpg-agent[30224]: chan_7 -> OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 <- OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 -> GETINFO pid gpg-agent[30224]: chan_7 <- GETINFO pid gpg-agent[30224]: chan_7 -> D 30224 gpg-agent[30224]: chan_7 -> OK gpg-agent[30224]: chan_6 <- D 30224 gpg-agent[30224]: chan_6 <- OK gpg-agent[30224]: chan_6 -> BYE gpg-agent[30224]: chan_7 <- BYE gpg-agent[30224]: chan_7 -> OK closing connection gpg-agent[30224]: handler 0x5573bdb32270 for fd 7 terminated
-> ps -A | grep 30224 30224 ? 00:00:00 gpg-agent
Looks as if gpg-agent is talking to itself?
Thus begs the question if I somehwo picked up an incompatibility between the gpg version that's on Leap adn Enigmail TB plugin?
The Enigmail plugin is version 1.9.1
OK, answering my own question, INCOMPATIBILITY: I removed the Enigmal version 1.9.1 plugin, which I presumably picked up when TB was restarted via the auto-upgrade mechanism and installed the enigmail package instead. This delivers version 1.8.2 of Enigmail and signing messages works again. Thus, those that have Enigmail and have auto-upgrade turned in in TB be aware that 1.9.1 does not work with Leap. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo
Robert Schweikert [18.03.2016 14:44]:
On 03/18/2016 09:19 AM, Robert Schweikert wrote:
On 03/16/2016 09:35 PM, Neil Rickert wrote:
On 03/16/2016 04:23 PM, Robert Schweikert wrote:
I restarted gpg-agent
/usr/bin/gpg-agent --sh --daemon --keep-display --write-env-file /home/rjschwei/.gnupg/agent.info-mountain:0
I'm not sure that would work.
Normally, GPG_AGENT_INFO is an environment variable that is inherited from the desktop startup. You would have to fix that at the command line, and then start Thunderbird at that command line so it would get the updated environment value.
The newer gpg in Tumbleweed puts the agent socked in $HOME/.gnupg, so that restarting probably works there. But that isn't in Leap 42.1
Thus, I suppose the instructions here [1] are somewhat useless as when starting the debugging session on the agent Thunderbird would not find the agent to communicate with I suppose.
I did try the debugging just in case but all that is produced is the following:
handler 0x5573bdb32270 for fd 7 started gpg-agent[30224]: chan_7 -> OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 <- OK Pleased to meet you, process 30224 gpg-agent[30224]: chan_6 -> GETINFO pid gpg-agent[30224]: chan_7 <- GETINFO pid gpg-agent[30224]: chan_7 -> D 30224 gpg-agent[30224]: chan_7 -> OK gpg-agent[30224]: chan_6 <- D 30224 gpg-agent[30224]: chan_6 <- OK gpg-agent[30224]: chan_6 -> BYE gpg-agent[30224]: chan_7 <- BYE gpg-agent[30224]: chan_7 -> OK closing connection gpg-agent[30224]: handler 0x5573bdb32270 for fd 7 terminated
-> ps -A | grep 30224 30224 ? 00:00:00 gpg-agent
Looks as if gpg-agent is talking to itself?
Thus begs the question if I somehwo picked up an incompatibility between the gpg version that's on Leap adn Enigmail TB plugin?
The Enigmail plugin is version 1.9.1
OK, answering my own question,
INCOMPATIBILITY:
I removed the Enigmal version 1.9.1 plugin, which I presumably picked up when TB was restarted via the auto-upgrade mechanism and installed the enigmail package instead. This delivers version 1.8.2 of Enigmail and signing messages works again.
Thus, those that have Enigmail and have auto-upgrade turned in in TB be aware that 1.9.1 does not work with Leap.
The package enigmail-1.9-1.1.x86_64 from obs:mozilla *does* work in Leap (with TB 38.6.0). Just my 2¢, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Neil Rickert -
Robert Schweikert -
Tom Kacvinsky -
Werner Flamme