Closed Bug 1844855 Opened 2 years ago Closed 2 years ago

Tab content does not persist after Thunderbird restart

Categories

(Thunderbird :: Mail Window Front End, defect)

Thunderbird 115
defect

Tracking

(thunderbird_esr102 unaffected)

RESOLVED WORKSFORME
Tracking Status
thunderbird_esr102 --- unaffected

People

(Reporter: hunter.james.p, Unassigned)

References

Details

(Whiteboard: [closeme 2023-12-20])

Steps to reproduce:

  1. Start Thunderbird (115 only).
  2. Open an email in a separate tab.
  3. Shut down Thunderbird.
  4. Start Thunderbird again.

Actual results:

The tab which should contain the email opened in step 2 is blank. It has no title and no body content.

Expected results:

In prior versions (102 and earlier) the open tab maintained the email title and body content across restarts.

Dupe of bug 1841411.

See Also: → 1846054

Hunter, does this still reproduce for you?

Flags: needinfo?(hunter.james.p)
Whiteboard: [closeme 2023-11-20]

In order to recheck this behavior I will need to reinstall thunderbird 115.x (currently 115.4.1-1, from the Arch Linux Extra repository). Before I do that I'd like to know if there has been some code fix added to the latest version which I need to test. Thanks.

Flags: needinfo?(hunter.james.p)

(In reply to Beaux from comment #3)

Before I do that I'd like to know if there has been some code fix added to the latest version which I need to test. Thanks.

Much has changed in four months. Whether your precise issue has gotten a patch is impossible to say.

Component: Untriaged → Mail Window Front End
Whiteboard: [closeme 2023-11-20] → [closeme 2023-12-20]

Okay, I ran version 115.5.1 and it seems to be working as expected - the open tabs, from the previous session, have the expected email content.

Thanks for the update.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME

This issue needs to be revisited. The same problem occurs with thunderbird-115.6.1-1 on Arch Linux (kernel: 6.6.10-arch1-1). Seem like it was never fixed.

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