GNOME Bugzilla – Bug 329546
Broken pipe with gpg when encrypting message with my pgp key
Last modified: 2021-05-19 12:27:41 UTC
Distribution: Ubuntu 6.04 (dapper) Package: Evolution Severity: Normal Version: GNOME2.13.90 unspecified Gnome-Distributor: Ubuntu Synopsis: Broken pipe with gpg when encrypting message with my pgp key Bugzilla-Product: Evolution Bugzilla-Component: ? Bugzilla-Version: unspecified Description: Description of Problem: I can send messages signed by my PGP key, but chen I want send encrypted messages, it displays "broken pipe with GPG" Steps to reproduce the problem: 1. Send an encrypted message 2. 3. Actual Results: error : "broken pipe with gpg" Expected Results: no error How often does this happen? everytime Additional Information: no ------- Bug created by bug-buddy at 2006-02-02 00:56 ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this.
I have this same problem on Fedora Core 5 with the following GnuPG packages: libgpg-error-1.1-1.2.1, gpgme-1.1.2-1.fc5, gnupg-1.4.2.2-2, gnupg2-1.9.20-3.fc5 The first time I tried to send a signed and encrypted message I got the error: Because "gpg: using classic trust model gpg: using subkey BD0004CB instead of primary key 9BFD7828 gpg: BD0004CB: There is no assurance this key belongs to the named user gpg: [stdin]: encryption failed: unusable public key ", you may need to select different mail options. The second time I got the same as the original reporter: "Because "Failed to execute gpg: Broken pipe", you may need to select different mail options."
Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/evolution/+bug/40326 "I can't cypher a message. An error message tells me: "Error running gpg:Broken pipe" , you may need to select different mail options. ... a temporary workaround for this issue which seems to work for me consists of edit > preferences > mail accounts > "target account" > edit > security > and ticking "always trust keys in my keyring when encrypting" i think this is an actual bug, i think it should ask if the particular key should be trusted each time if this is not ticked instead of passing "broken pipe""
the problem is that gpg exists and doesn't tell us the problem or even prompt us if the key should be trusted "this one time", so likely unfixable. (yes yes, I see that it pronts text to stderr that says the key is untrustable, but that is not machine parseable)
(In reply to comment #3) > the problem is that gpg exists and doesn't tell us the problem or even prompt > us if the key should be trusted "this one time", so likely unfixable. > > (yes yes, I see that it pronts text to stderr that says the key is untrustable, > but that is not machine parseable) > So what will be done about this bug? If it is unfixable then encryption should be removed altogether from Evolution. There is no point in having features that do not work or only work after changing options.
(In reply to comment #3) > the problem is that gpg exists and doesn't tell us the problem or even prompt > us if the key should be trusted "this one time", so likely unfixable. I believe I've seen this in other clients. At least mutt asks me every time whether I want to trust a key. I'm not sure about it, but I think Thunderbird (+Enigmail) will always trust all the keys; perhaps not the best way, but at least it works out of the box. > (yes yes, I see that it pronts text to stderr that says the key is untrustable, > but that is not machine parseable) Why wouldn't that be possible? I did that some years ago (admittedly an ugly hack). It's not that the message need be interpreted, if it was just printed next to "Broken pipe", which is the kind of error message that deeply disturbs me.
Personally I have not seen this problem for ages. Is this still a problem for anybody using Evolution 3.0.3 or 3.2.2?
Still a problem (at least the error messages telling us things like "unusable public key").
I've seen bug reports to deal with the wording of error messages. This particular bug, "broken pipe" and not getting a machine readable error from gpg, seems to have disappeared. It will most likely be a thing of the past if Evolution starts using gpgme instead of calling the gpg binary itself.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new bug report ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.