288600 - TB crashes when signing or verifying the signature of messages

Status: RESOLVED EXPIRED

(Thunderbird :: General, defect)

Description

[Peter Dedecker]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050327 Firefox/1.0.2
Build Identifier: Thunderbird version 1.0.2

When I compose a message and press the "send" button, TB crashes.  When I turn
off digitally signature, TB doesn't crash.  The same thing happens when
selecting a message that's digitally signed.

Reproducible: Always

Steps to Reproduce:
1. Compose a new message
2. Make sure digitally signature (enigmail) is on
3. Press "send"

Actual Results:  
TB crashes

Expected Results:  
The message should be sent without problems

This is the content of the file ~/.enigmail.log/enigdbug.txt





enigmail.js: Logging debug output to ~/.enigmail.log/enigdbug.txt
enigmail.js: Enigmail version 0.91.0.0
enigmail.js: OS/CPU=Linux i686
enigmail.js: Platform=X11
enigmail.js: composeSecure=true
enigmail.js: Enigmail.initialize: gEnvList =
DISPLAY=:0.0,HOME=/home/peddecke,LC_ALL=nl_BE@euro,LC_CTYPE=nl_BE@euro,LOGNAME=peddecke,LD_LIBRARY_PATH=/usr/li
b/MozillaThunderbird:/usr/lib/MozillaThunderbird/plugins,MOZILLA_FIVE_HOME=/usr/lib/MozillaThunderbird,PATH=/usr/bin:/bin:/usr/X11R6/bin:/usr/kde/3.4/bin:/u
sr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.3.5:/opt/Acrobat5:/opt/sun-jdk-1.4.2.07/bin:/opt/sun-jdk-1.4.2.07/jre/bin:/opt/sun-jdk-
1.4.2.07/jre/javaws:/opt/sun-j2ee-1.3.1/bin:/usr/qt/3/bin:/usr/kde/3.4/bin:/usr/kde/3.3/bin:/usr/kde/3.2/bin:/opt/vmware/bin,PWD=/home/peddecke,SHELL=/bin/b
ash,USER=peddecke
enigmail.js: ResolvePath: filePath=gpg
EnigmailAgentPath=/usr/bin/gpg

enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --version
gpg (GnuPG) 1.4.1
Copyright (C) 2005 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512
Compression: Uncompressed, ZIP, ZLIB

enigmail.js: Enigmail.stillActive:
enigmail.js: Enigmail.initialize: END
enigmailMsgComposeOverlay.js: EnigEditorGetContentsAs
enigmailMsgComposeOverlay.js: enigGenericSendMessage: msgType=0
  Identity = [nsIMsgIdentity: id1]
enigmailMsgComposeOverlay.js: enigModifyCompFields: otherRandomHeaders =
X-Enigmail-Version: 0.91.0.0

enigmailMsgComposeOverlay.js: enigEncryptMsg: msgType=0, gEnigSendMode=1
enigmailMsgComposeOverlay.js: enigEncryptMsg: currentId=[nsIMsgIdentity: id1],
[e-mail]
enigmailMsgComposeOverlay.js: enigGetAccDefault: identity=id1 value=enabled
enigmailMsgComposeOverlay.js: enigEncryptMsg:gMsgCompose=[xpconnect wrapped
nsIMsgCompose]
enigmailMsgComposeOverlay.js: enigGetAccDefault: identity=id1 value=signPlain
  signPlain=true
enigmailMsgComposeOverlay.js: enigEncryptMsg: toAddr=[e-mail]
enigmailMsgComposeHelper.js: getRecipientsKeys:
emailAddrs=[e-mail]
enigmail.js: getRulesData
enigmail.js: loadRulesFile
enigmail.js: getRulesFile
enigmailMsgComposeOverlay.js: hasAttachments = false
enigmailMsgComposeOverlay.js: enigEncryptMsg: Using EnigMime, flags=225
enigmailMsgComposeOverlay.js: enigEncryptMsg: oldSecurityInfo = [xpconnect
wrapped nsIMsgSMIMECompFields]
enigmailMsgComposeOverlay.js: enigEncryptMsg: securityInfo = [xpconnect wrapped
nsIEnigMsgCompFields]
enigmailMsgComposeOverlay.js: enigEncryptMsg: enabled quoted-printable

Comment 1

[Ray Booysen]

Reporter, can you get a TalkbackID for this crash and post it?

Comment 2

[Ray Booysen]

As a second comment, this sounds like a problem with the extension not with
Thunderbird.  You should post this bug with enigmail first to identify the
source of the error.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.