T 1.0 crashes when sending encrypted email

RESOLVED EXPIRED

Status

Thunderbird
General
--
critical
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: KevDog, Assigned: Scott MacGregor)

Tracking

({crash})

x86
Windows XP
crash

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
Trying to send encrypted email via a self signed ca and pck12 file.  Able to
send self-signed email but not encrypted email.  Seen other bugs related to this
problem.

Comment 1

14 years ago
can you install talkback and get an incident id?
(Reporter)

Comment 2

14 years ago
Here is the bug report you requested that Thunderbird generates.  Again
Thunderbird crashes when sending ssl encrypted email.  I am running WinXP with
cygwin installed.  I am not sure if there is a conflict.

Link to report file: http://gohilton.com/bugreport.txt

Comment 3

14 years ago
KevDog: Could you please send incident report as is described on
<http://www.mozilla.org/quality/qfa.html> and provide its ID?
Severity: normal → critical
Keywords: crash
(Reporter)

Comment 4

14 years ago
How do I find the incident ID??? It is not contained in the file being sent??
Please help me so I can help you.  The link provided in another post simply
explained use of the feedback agent and did not specifically describe how to get
the incident ID.  
(Reporter)

Comment 5

14 years ago
Again -- I am sorry I can not help with the incident ID.  I started the talkback
program, and no incidents are shown.  Im sorry I can not be more of a help. 
Again the behaivor I am having is upon attempted delievery of an ssl-encrypted
emain (right after I push the send button), thunderbird crashes and I receive
the mozilla quality feedback agent popup.  I posted what I am sending to the
feedback service, however again, no error is logged or shown through the
talkback program

Thanks for the help

Comment 6

13 years ago
KevDog: I'm sorry, but I can't help you more. Something must be going wrong,
because normally Talkback lists all captured incidents.

Maybe you should retry and follow these steps after crash occur and MQF Agent
(aka Talkback) appear:
1. if "Welcome to the Mozilla Quality Feedback Agent" dialogs appear, click
   on "Next" button on all three dialogs
2. on next dialog, please enter your e-mail (optional), leave URL field blank
   and as description write "bug 276620"
3. submit this report by button "Send"
4. let Talkback to submit incident to Mozilla Foundation server
5. run "talkback.exe" in your Thunderbird's components subdirectory
6. ... and I hope you will see Talkback incident id.
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.