Open Bug 1823095 Opened 2 years ago Updated 10 months ago

`Check for new messages every xx minutes` stops happening automatically after OS was sleeping

Categories

(Thunderbird :: General, defect, P3)

Thunderbird 112
x86_64
macOS

Tracking

(Not tracked)

People

(Reporter: mitra_lists, Unassigned)

References

Details

(Keywords: dupeme, Whiteboard: [snnot3p])

Thunderbird seems to be getting into a state where it stops fetching new messages automatically.

The symptoms I noticed were ... opened machine (restored from sleep).
Navigated to TB
No new messages shown - which was strange as had been overnight
Did a Get New Messages - and it fetched just fine.

I am pretty sure that the machine had been open a lot longer than the 5 minute interval between searches.

This might be hard to repeat, as I'm not sure what puts it into that state, and probably wouldn't report it except for the significant changes to TB which make odd bugs more likely; so I'm leaving this as a placeholder in case anyone else notices the same behavior.

Thanks Mitra, nice move!
I would hope/suspect that problems with automatically getting messages are not caused by the Supernova 3-pane UI, so this might be a pre-existing problem. I believe there's a similar bug on record which I can't find right now.

(In reply to Mitra Ardron from comment #0)

Thunderbird seems to be getting into a state where it stops fetching new messages automatically.
I am pretty sure that the machine had been open a lot longer than the 5 minute interval between searches.

I'm surprised at your summary, "Getting all messages" stops happening automatically, which may be based on a misconception:
Thunderbird does not have a feature (yet?) to "Automatically check for new messages on all accounts every nn minutes" (as if you were pressing the Get [all] messages button every nn minutes). Instead, checking for new messages automatically is based on the respective **per-account** pref labeledCheck for new messages every xx minutes`. You may have different checking intervals for different accounts of yours, and (hopefully) those would all be honored.

  • Which account types are affected? (POP/IMAP)
  • What's your Check for new messages every xx minutes setting on the failing accounts?
  • Does this happen when TB sleeps in ≡ > Help > Troubleshoot Mode…?
  • When this occurs, does your OS sleep (PC remains on) or hibernate (suspend to disk)?
Flags: needinfo?(mitra_lists)
Keywords: dupeme
Summary: "Getting all Messages" stops happening automatically. → `Check for new messages every xx minutes` stops happening automatically after OS was sleeping
Severity: -- → S3
Priority: -- → P3
Whiteboard: [snnot]
See Also: → 1824422

Yes @Thomas, you are correct, and my bug report wasn't as helpful as it could be.

The problem was that it wasn't - still doesn't appear to be - checking the accounts based on the schedule.

The main account is IMAP, checking every 5 mins, its a Mac, and the issue isn't that it doesn't occur WHILE sleeping, its that it doesn't occur on return from sleep. I'm pretty sure old TB would have checked immediately on restore from sleep if the timer for that account had expired.

I'm off-grid for next week, if this still persists when I return I can look deeper if its not trivial to repeat.

Flags: needinfo?(mitra_lists)

Let us know about 113. Thanks

Flags: needinfo?(mitra_lists)
Whiteboard: [snnot] → [snnot3p]

Yes - it is still happening.

STR
Account Settings - confirm set for 5 minute poll
Close laptop (goes to sleep)
Send self an email from somewhere else
Wait some period of time significantly longer than 5 minutes
reopen laptop (wakes up)
connect to internet
navigate to TB
notice that email is not there
File / Get New Messages / All Accounts
Notice it retrieves message sent above.

What I'm curious about .... is it possible that TB is not checking whether its been more than 5 mins since a successful check when it gets its net connection back?

Flags: needinfo?(mitra_lists)

Mac users, is anyone else able to reproduce?

See Also: → 1850679
You need to log in before you can comment on or make changes to this bug.