Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Learn More

New Message Counter Bugged since coulple of releases

  • 1 odgovor
  • 1 ima to težavo
  • 6 ogledov
  • Zadnji odgovor od Camrais

more options

Hi there,

since a couple of releases since I installed thunderbird on my MacBook, I got the problem that the counter displays 99+ unread messages when everything is read. It only transforms to a no red dot icon when I have 3 unread messages across my accounts, and then if more come in starts to count up. I waited thinking it's just a bug on one release (as it suddenly started doing it after an update, but I don't remember what version that was) but after receiving the newest update (Version 102.9.1 (64-Bit)) it is still not fixed.

I have tried changing the system settings for the icon (disabling this red dot and then turning it back on) but it didn't work.

Any other suggestions?

Hi there, since a couple of releases since I installed thunderbird on my MacBook, I got the problem that the counter displays 99+ unread messages when everything is read. It only transforms to a no red dot icon when I have 3 unread messages across my accounts, and then if more come in starts to count up. I waited thinking it's just a bug on one release (as it suddenly started doing it after an update, but I don't remember what version that was) but after receiving the newest update (Version 102.9.1 (64-Bit)) it is still not fixed. I have tried changing the system settings for the icon (disabling this red dot and then turning it back on) but it didn't work. Any other suggestions?

Izbrana rešitev

As of the latest Thunderbird Update (120.10.0) and MacOS Release (13.3.1 (22E261)) it seems to be finally fixed :)

Preberite ta odgovor v kontekstu 👍 0

Vsi odgovori (1)

more options

Izbrana rešitev

As of the latest Thunderbird Update (120.10.0) and MacOS Release (13.3.1 (22E261)) it seems to be finally fixed :)