Open Bug 1911040 Opened 7 months ago Updated 4 months ago

blank mail tab after automatic upgrade to Thunderbird 128.0.1esr

Categories

(Thunderbird :: Mail Window Front End, defect)

Thunderbird 128
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: philipp, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

Attached image blank mail window

Steps to reproduce:

Thunderbird upgraded to 128.0.1esr unintentionally after I opened the "About dialogue". (Unlike with earlier ESR releases, I did not receive a promt to update like mentioned in https://blog.thunderbird.net/2024/07/thunderbird-monthly-development-digest-july-2024/)

Downgrading to 115.13.0 works and the mail windows appears as expected.

I'll be happy to provided helpful information.

Actual results:

Thunderbird 128 shows a completely blank mail tab.

In the account settings there are "no folders available" to choose for e.g. drafts.
Address book tab and content shows as expected.
Calendar and task tabs show, but the content of synced calendars is not displayed.

Expected results:

The mail window should show as expected.

Attachment #9417198 - Attachment description: Screenshot 2024-08-01 102047.png → blank mail window

additional information:

  • starting in Safe-Mode did not change anything.
  • I use maildir IMAP accounts
Blocks: tb128found

Do you get any relevant errors in the Error Console? Ctrl+Shift+J

I get the following warning in dev tools console for the emails that show a blank window:

This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”.

I fixed this situation after restore to 115.10.1, and all the things back.

A fresh profile seems to have fixed the issue for me (128.1.0esr).

(Before trying a new profile, I exported a problematic email as an .eml file (using another working client). Re-importing this local file to another TB folder via drag&drop showed the content again, while the original version still had the problem.)

And as I was writing this, I tried moving the problematic email from one folder to another - now it is readable again!
#workaround

(In reply to Magnus Melin [:mkmelin] from comment #3)

Do you get any relevant errors in the Error Console? Ctrl+Shift+J

I am away from my installation for the next 2 1/2 weeks and can only report back afterwards.

bug #1911951 seems very similar if not the same.

See Also: → 1911951

Screenshot looks the same as it did in my case described in #1911951, which was worked around by removing hostname setting for an old server entry in prefs.js. That was not related to a particular message as the mbox files were empty.

Philipp, do one of your accounts use an invalid hostname? If so, what?

Flags: needinfo?(philipp)

(In reply to Magnus Melin [:mkmelin] from comment #9)

Philipp, do one of your accounts use an invalid hostname? If so, what?

I also use the localfolders extension, so the issue is analogous to what kompre describes:
https://bugzilla.mozilla.org/show_bug.cgi?id=1911951#c15

The generated hostnames are derived from the account names, in my case they contain an email adress and by that an '@'.
I manually replaced '@' in those hostnames by '(at)' and Thunderbird 128 back to work.

Flags: needinfo?(philipp)

(In reply to Philipp Schlesinger from comment #10)

I also commented with further information at:
https://github.com/cleidigh/Localfolder-TB/issues/83#issuecomment-2324167499

Bug 1911951 will make it so that invalid hostnames in the prefs are handled gracefully. That should sort this bug out as well.

The patch that went into Thunderbird 128.2.2esr handles invalid hostnames like "archive mail(at)address.com" gracefully by replacing, but still fails to cope with "archive mail(@address".

So it does not solve the situation described in comment #10.

I don't know exactly what the add-on does, but it should not be using invalid hostnames. (On daily it's much stricter still.)
I would consider that an add-on bug.

Sure, it is an add-on bug and should in future be validated by the add-on.

But as the hostname entries already exist, the patch to mitigate this should maybe also cope with entries containing an '@'.
As a last resort, it cloud point to the offending line in prefs.js instead of leaving Thunderbird with a blank mail tab.

Attached file log
Hi, same trouble for me with `Thunderbird 128.3.1esr 20241009142959 20241009142959`. Safe-Mode did not change anything, I use IMAP, and the issue is present on some received massages and sent messages. There is my full thunderbird log: ``` ```

Hi there,

Same trouble for me with Thunderbird 128.3.1esr 20241009142959 20241009142959.
Safe-Mode did not change anything, I use IMAP, and the issue is present on some received massages and sent messages.

See Also: → 1904211
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: