Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

New Message Counter Bugged since coulple of releases

  • 1 odgovor
  • 1 ima ovaj problem
  • 5 prikaza
  • Posljednji 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?

Izabrano rješenje

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

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (1)

more options

Odabrano rješenje

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