Closed Bug 227355 Opened 22 years ago Closed 21 years ago

thunderbird crashes when trying to read an email with attached web page

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: joerg.buesse, Assigned: mscott)

References

()

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 see steps to produce i'tried Thunderbird Version 0.4alpha and 0.3 -> same result -> crash Reproducible: Always Steps to Reproduce: 1. Compose EMail (Write) 2. Attach Webpage 3. http://www.mozilla.org 4. To:5 <Your EMail Adress> 5. Send 6. Get Mail 7. Try to read the new EMail sent above Actual Results: crash Expected Results: what do you think ?
seems to be duplicate, sry searched for: mail crash http but didn't found matching bugs
Anyone trying to solve this bug ?
I can't re-produce the bug on thunderbird 0.6.
Jorg: Are you able to reproduce with Mozilla Thunderbird 0.7.3? Could you provide TalkBack incident ID in such case?
Keywords: crash
No, I can't reproduce the Bug, obviously the problem was fixed.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
(In reply to comment #5) > No, I can't reproduce the Bug, obviously the problem was fixed. I've to add: I'm using Firefox 0.9.3 for Linux
(In reply to comment #6) > (In reply to comment #5) > > No, I can't reproduce the Bug, obviously the problem was fixed. > > I've to add: I'm using Firefox 0.9.3 for Linux Sorry again, I don't know what's up with me .... *aaarghhh*. I'm using Thunderbird 0.7.1 (20040626) and the problem is not reproduceable. I believe it was fixed.
Not patch, not FIXED. Reopen to re-resolve.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Marking WFM regarding reporter's last comments.
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.