Closed Bug 1917006 Opened 1 year ago Closed 1 year ago

REOPENING "mail from MEGA crashing thunderbird when displayed as full HTML"

Categories

(Thunderbird :: General, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: felipelorenzzon, Unassigned)

Details

this is reopening of bug available in https://bugzilla.mozilla.org/show_bug.cgi?id=1761703.

System information

Operating System: Manjaro Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-10-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 7580

115.14.0 (64 bits) Mozilla Thunderbird for Manjaro LinuxManjaro - 1.0

Steps to reproduce:

I click on the mail from MEGA.nz in Thunderbird for resetting my password. I have not attached it to the bug report due to personal information. With the setting for display on Original HTML, it crashes Thunderbird. The old bug had been closed, but it's been two years a few generations. If this is a problem caused by Manjaro, I'll them know in their forums.

Actual results:

Thunderbird crashes

terminal shows this after I click on the mail:

JavaScript error: chrome://messenger/content/preferences/general.js, line 2071: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIObserverService.removeObserver]
Exiting due to channel error.
zsh: segmentation fault (core dumped)  thunderbird

If I display mails as Simple HTML or as Plain Text, Thunderbird does not crash when I click on the mail and I can read the content.

Expected results:

The mail should be displayed, and Thunderbird should not crash. The web client for gmail does not crash.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME

I've installed the flatkpak version of Thunderbird just to test this. In the most recent version, 128, the bug has been resolved.

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