We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

The recent update broke Thunderbird.

  • 1 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan jimpem

jimpem
jimpem
more options

The update that dropped a few days ago just automatically installed today. (No complaints about autoinstall.) With the new update, Thunderbird opens and allows me to view one message, but it won't change to a different message. If that first message happened to have an attachment, it won't open the attachment. I try to have it close and reopen with addons disabled, but it freezes (or at least closes the UI but stays running in the background so it can't reopen). How do I fix it?

The update that dropped a few days ago just automatically installed today. (No complaints about autoinstall.) With the new update, Thunderbird opens and allows me to view one message, but it won't change to a different message. If that first message happened to have an attachment, it won't open the attachment. I try to have it close and reopen with addons disabled, but it freezes (or at least closes the UI but stays running in the background so it can't reopen). How do I fix it?

Alle antwurden (1)

jimpem
jimpem Fraacheigener
more options

Well, it seems after several tries of stopping and starting Thunderbird, it managed to work out its own problem. I don't know why it was wonky the first several times - maybe it was processing some newly incompatible addons and took a few times to get them all disabled? Who knows. It works now.