Bug 622225 - gpg2 crashes when trying to sign a message within enigmail
Summary: gpg2 crashes when trying to sign a message within enigmail
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnupg2 (Show other bugs)
(Show other bugs)
Version: 14
Hardware: All Linux
low
medium
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-08 07:57 UTC by Joachim Backes
Modified: 2010-08-13 12:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-13 07:29:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Joachim Backes 2010-08-08 07:57:06 UTC
Description of problem:
I have the enigmail-1.1.2 extension installed in thunderbird. I try to sign an email, but this is rejected by an error popup:
------------------------------------------------------
Send operation aborted.

Error - encryption command failed

gpg command line and output:
/usr/bin/gpg
gpg: problem with the agent: No pinentry
gpg: skipped "0x6574AACF": General error
gpg: [stdin]: clearsign failed: General error
--------------------------------------------------------
Version-Release number of selected component (if applicable):

gnupg2-2.0.14-4.fc14.i686

How reproducible:
always

Steps to Reproduce:
1.Create a new message
2.OpenOGP->Sign message
3.
  
Actual results:
See Output under "description"

Expected results:


Additional info:
I tried this with thunderbird-3.1.2 from mozilla.org. But having the exactly the same results with thunderbird-3.1.1 from the F14-repos.

Comment 1 Rex Dieter 2010-08-08 12:49:10 UTC
Do you have either pinentry-gtk or pinentry-qt installed?  (If not, install one of these and try again).

Comment 2 Joachim Backes 2010-08-08 15:19:24 UTC
(In reply to comment #1)
> Do you have either pinentry-gtk or pinentry-qt installed?  (If not, install one
> of these and try again).    

Hi Rex,

both, pinentry-gtk and pinentry-qt, were and are installed.

Comment 3 Rex Dieter 2010-08-08 15:33:44 UTC
Is gpg-agent running?

(or perhaps seahorse-agent , though if the latter, it tries to emulate gpg-agent and I'm not all that familiar with it)

Comment 4 Joachim Backes 2010-08-08 16:55:48 UTC
(In reply to comment #3)
> Is gpg-agent running?
> 
> (or perhaps seahorse-agent , though if the latter, it tries to emulate
> gpg-agent and I'm not all that familiar with it)    

Not immediately after thunderbird is started, but it is started if I begin to compose a mail.

Comment 5 Joachim Backes 2010-08-13 05:33:33 UTC
Signing and encrypting/decrypting now work with gnupg2-2.0.16-1.fc14.i686.

Comment 6 Joachim Backes 2010-08-13 11:18:16 UTC
I was is bit too quick: signing and encrypting a message, and the sending it: An error popup appears:

Send operation aborted.

Error - encryption command failed

gpg command line and output:
/usr/bin/gpg
gpg: problem with the agent: End of file
gpg: skipped "0x6574AACF": Operation cancelled
gpg: [stdin]: sign+encrypt failed: Operation cancelled


If I press the send button again, the message is sent and can be decrypted by the recipient.

Remark: This only happens once after a fresh thunderbird start. Then, after thunderbird runs, having no more problems with sending of signed/encrypted messages.

Comment 7 Tomas Mraz 2010-08-13 12:18:27 UTC
As there will be change back to gpg-1 for the gpg binary, this problem will probably disappear anyway.

Comment 8 Joachim Backes 2010-08-13 12:48:14 UTC
(In reply to comment #7)
> As there will be change back to gpg-1 for the gpg binary, this problem will
> probably disappear anyway.    

This will happen in F14?

Comment 9 Rex Dieter 2010-08-13 12:54:10 UTC
hopefully yes (most of the work is being done by others).


Note You need to log in before you can comment on or make changes to this bug.