Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Newsgroup access hangs after upgrade to version 102

  • 10 отговора
  • 3 имат този проблем
  • 26 изгледи
  • Последен отговор от Dennis Han

more options

For years I have been using Thunderbird on Windows (10 and 11) to access a newsgroup via the news.individual.net server. After I upgraded Thunderbird from version 91 to 102, I had the problem that trying to get new messages would just cause Thunderbird to stall., with the oscillating dot in the title bar. If I ask it to refresh the list of newsgroups, it tells me "Error retrieving items from the server".

I deleted the account and recreated it. It found my newsgroup fine and downloaded messages - once. If I tried to get more, it was back to the stall.

I have tried switching between SSL and non-SSL access, to no effect. "Troubleshoot Mode" shows the same behavior. "Clear Startup Cache" also has no effect. This server does require a login.

For years I have been using Thunderbird on Windows (10 and 11) to access a newsgroup via the news.individual.net server. After I upgraded Thunderbird from version 91 to 102, I had the problem that trying to get new messages would just cause Thunderbird to stall., with the oscillating dot in the title bar. If I ask it to refresh the list of newsgroups, it tells me "Error retrieving items from the server". I deleted the account and recreated it. It found my newsgroup fine and downloaded messages - once. If I tried to get more, it was back to the stall. I have tried switching between SSL and non-SSL access, to no effect. "Troubleshoot Mode" shows the same behavior. "Clear Startup Cache" also has no effect. This server does require a login.

Избрано решение

This sounds like bug https://bugzilla.mozilla.org/show_bug.cgi?id=1745033 A fix went into TB104.0 beta, to be released sometime next week. When it will show up in TB 102 I don't know. For the time being you can try to remove the primary password in TB 102/103 beta or switch back to the old NNTP implementation.

Прочетете този отговор в контекста 👍 1

Всички отговори (10)

more options

No replies - sigh. I downloaded the 103 beta and it does not have this problem.

more options

Spoke too soon. If I installed the beta side-by-side and added my news account to it, it worked. But if I then imported my profile from the release version, the problem reappeared. I have tried deleting and re-adding the account with no success.

more options

Избрано решение

This sounds like bug https://bugzilla.mozilla.org/show_bug.cgi?id=1745033 A fix went into TB104.0 beta, to be released sometime next week. When it will show up in TB 102 I don't know. For the time being you can try to remove the primary password in TB 102/103 beta or switch back to the old NNTP implementation.

more options

Yes, that is indeed the problem. Removing the primary password for now works. Thanks.

more options

I got version 104 today and the problem is indeed resolved. Thanks again.

more options

I am using version 102.1.2 (64-bit) with no primary password and my newsgroups are not updating. I tried adding a primary password, closing and restarting Thunderbird, removing the primary password, then closing and restarting again. Still no access to newsgroups. I also tried changing mailnews.nntp.jsmodule to false but still no access. Any suggestions besides getting the version 104 beta?

more options

Upgrading to beta is always a bad solution, as betas have their own problems. And you can't go back from a beta. I suggest you verify that you have set authentication, since it defaults to off.

more options

If you are describing mail.server.default.always_authenticate, it made no difference to set it to true.

more options

I was referring to the authenticate setting in thunderbird server settings for account.

more options

Authentication was already set to true, so I tried false and it made no difference.