Closed Bug 1816684 Opened 2 years ago Closed 2 years ago

Email notification displays old messages

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: theman, Unassigned)

Details

Steps to reproduce:

I use Thunderbird in the background. There was no particular user action in this case.

Actual results:

Using verion 102.7.1 (64-bit), OS is Manjaro with 5.15.91-1-MANJARO which uses Dunst for notifications. Thunderbird runs usually in the background. A sporadic behavior is that the notifications for "new" emails show emails that were received last night or some hours ago. Also, the notifications do not arrive in aggregate, but one email at a time.

This appears to be a regression that was introduced at some point since I clearly recall this wasn't so in the past.

Expected results:

As a user I expect that all notifications for email that I haven't read and that are newly received by Thunderbird should be shown in one notification when Thunderbird starts. From that point on I would expect Thunderbird to notify my only about newly received messages.

TB uses libnotify. We don't know how and what Dunst listens to.
Did you first report this to Manjaro and were asked to report here instead? Please link to that report. Thanks.

Flags: needinfo?(theman)

I did not report it on Manjaro. TB is the anomaly here since all other notifications I get from Dunst seem to be in order temporally, so my guess was to open a report here rather than in Manjaro. If you feel this is misplaced or out of scope, feel free to close this issue (but also suggest where this would be more appropriate to open).

Does this also reproduce when using version 115 started in Help > Troubleshoot Mode?
If it does, and you have not already done so, please list complete steps to reproduce.

Whiteboard: [closeme 2023-10-01]

Resolved per whiteboard

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(theman)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2023-10-01]
You need to log in before you can comment on or make changes to this bug.