Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thunderbird (various versions) Hangs on opening in Ubuntu 22.04.3 LTS after latest updates

  • 1 reply
  • 1 has this problem
  • 33 views
  • Last reply by cl1

more options

After applying the latest updates to Ubuntu 22.04.3 LTS today, I find that ThunderBird will load and then enter a busy state where the system asks if I want to terminate or wait for ThunderBird.

After waiting quite some time, it is apparent that perhaps it is in vain. I have tried a few different versions: The initially installed: 115.5.0 The latest: 121.0b1 and previous: 115.4.3

All seem to exhibit similar behavior with my previously working profile.

The program loads, the preview screen draws, an open tab appears to try to load, and a few seconds after launch, things hang up.

Anyone else noticing issues?

After applying the latest updates to Ubuntu 22.04.3 LTS today, I find that ThunderBird will load and then enter a busy state where the system asks if I want to terminate or wait for ThunderBird. After waiting quite some time, it is apparent that perhaps it is in vain. I have tried a few different versions: The initially installed: 115.5.0 The latest: 121.0b1 and previous: 115.4.3 All seem to exhibit similar behavior with my previously working profile. The program loads, the preview screen draws, an open tab appears to try to load, and a few seconds after launch, things hang up. Anyone else noticing issues?

Chosen solution

Seems that replacing the session.json file for the profile with the session.json.backup (essentially removing the reference to the previously open tab) has, at least for now, cleared up this issue.

Will be watching the system behavior. and report back if the situation recurs.

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

Seems that replacing the session.json file for the profile with the session.json.backup (essentially removing the reference to the previously open tab) has, at least for now, cleared up this issue.

Will be watching the system behavior. and report back if the situation recurs.