Closed Bug 1827285 Opened 2 years ago Closed 2 years ago

Thunderbird not displaying updates to Usenet after sitting idle for awhile on Mac running Mojave

Categories

(MailNews Core :: Networking: NNTP, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bcfd36, Unassigned)

Details

(Whiteboard: [needs protocol log])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.3 Safari/605.1.15

Steps to reproduce:

This has happened several times. I am on a MacIntosh running Mojave. The Thunderbird version is 102.9.1 (64-bit).

In the last week or so but no more than a month, Thunderbird (TB) will stop displaying Usenet messages after sitting idle for awhile.

  1. Bring up TB.
  2. Read Usenet messages on multiple groups
  3. Go away for the evening
  4. Resume using TB the next morning
  5. Discover that I can no longer display any new messages
  6. Quit TB
  7. Restart TB and resume reading messages.

The only way I have found to correct the problem is to quit TB via the menu and restart TB. Then it works fine.

Actual results:

I use Thunderbird as a newsreader for Usenet.

After using TB during on Day 1, when I come back and use it on Day 2 and cannot display any messages, neither new ones that have come in or old ones that I have displayed previously.

Expected results:

TB should have picked up where it left off.

This has happened every day for at least the last several days.

I cannot locate, so far, any error log or the like.

Component: Untriaged → Networking: NNTP
Product: Thunderbird → MailNews Core

Thanks for the report. Please use https://wiki.mozilla.org/MailNews:Logging to get an nntp log, and use Attach New File to this bug report. Thanks

Flags: needinfo?(bcfd36)
Whiteboard: [needs protocol log]

The problem seems to have gone away.

Sorry about that.

Flags: needinfo?(bcfd36)

Thanks for the update

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.