1976629 - Old tasks (unfinished) no longer ring (missed reminders no longer shown)

Status: RESOLVED DUPLICATE of bug 1972904

(Calendar :: Alarms, defect)

Description

[Totoche2607]

Steps to reproduce:

I'm on 140.0esr, but this problem also exists on release; since an update at the beginning of the year (March, I think, but I'm not sure...).
That's what made me switch to 128.xesr, thinking I could avoid this very annoying problem for me and my appointment reminders.

Personally, I assume that an unfinished task should ring if no end date has been set for it...
(otherwise I don't see the point!)

Actual results:

Thunderbird-Lightning no longer alerts me, ring, when:

-tasks occur while Thunderbird is closed, so at startup
-older tasks with times/dates have passed (without end date) too

Expected results:

-previously, task ring at startup if the alert was triggered when TB was closed (similar to a reminder)
-previously older task without end date ring periodically

Comment 1

[Magnus Melin [:mkmelin]]

The default value for "Show missed reminders for writable calendars" changed to false (bug 1934069). You can change it back in the settings.

Comment 2

[Totoche2607]

Thank you for your reply, I will move on to the other topic...

But just to let you know that it's not working... I enabled the option, created a new 'test' task for one minute later, closed TB, and restarted it five minutes later: no notification at startup...

Comment 3

[Totoche2607]

Hi,

the "Show missed reminders for writable calendars" option in setting does not work for tasks, just for events...

So I think that 1934069 generated a bug for tasks that are overdue/outdated (with no end date...)
Either this option should be valid for tasks and events, or there should be two different ones.

ty

Comment 4

[Corey Bryant]

Re-opening based on comments 2 and 3.

Comment 5

[Corey Bryant]

Vlad/Ramona, can you recreate this?

Comment 6

[Ramona Gavrilescu]

Hello Corey!

I have check this issue on Win 10 and MacOs Sequoia 15.5. and did not encounter this behaviour.
I have checked on the following TB versions:
128.9.2esr 20250415075302
128.11.1esr( 20250606210711)
128.12.0esr(20250627203320)
140.0.1esr(20250709213912)

On Win 10 the reminder was shown at startup, on macOs it was displayed after approx 10 - 15 min from startup.
I have tested various scenarios for task, older tasks with different times, dates that have passed.

Comment 7

[Totoche2607]

(I'm on Windows 11)
After your message, I ran another test with a clean version (140.0.1 release and esr): same result, it doesn't work: no alerts.

To reproduce: fresh installation, creation of a first task to be able to have the ‘calendar’ settings (otherwise absent)
activation of ‘Show missed reminders for writable calendars’. restart

for example: it is 4:13 a.m. creation of a ‘test1’ task for 4:10 a.m.: it should ring as soon as I save: This is not the case.
Creation of a task ‘test2’ for 4:20 a.m., then close TB and restart at 4:25. It should alert/ring when restarting, but it doesn't...

(screenshot : https://ibb.co/svpzj6MW)

(For information, I also did a clean install with 128.x: it works...)

Comment 8

[Totoche2607]

(In reply to Totoche2607 from comment #7)

Hi, After your message, I ran another test with a clean version (140.0.1 release and esr): same result, it doesn't work: no alerts.
(I'm on Windows 11)

To reproduce: fresh installation, creation of a first task to be able to have the ‘calendar’ settings (otherwise absent)
activation of ‘Show missed reminders for writable calendars’. restart

for example: it is 4:13 a.m. creation of a ‘test1’ task for 4:10 a.m.: it should ring as soon as I save: This is not the case.
Creation of a task ‘test2’ for 4:20 a.m., then close TB and restart at 4:25. It should alert/ring when restarting, but it doesn't...

(screenshot : https://ibb.co/svpzj6MW)

(For information, I also did a clean install with 128.x: it works...)

Comment 9

[Totoche2607]

Hi, After your message, I ran another test with a clean version (140.0.1 release and esr): same result, it doesn't work: no alerts.
(I'm on Windows 11)

To reproduce: fresh installation, creation of a first task to be able to have the ‘calendar’ settings (otherwise absent)
activation of ‘Show missed reminders for writable calendars’. restart

for example: it is 4:13 a.m. creation of a ‘test1’ task for 4:10 a.m.: it should ring as soon as I save: This is not the case.
Creation of a task ‘test2’ for 4:20 a.m., then close TB and restart at 4:25. It should alert/ring when restarting, but it doesn't...

(screenshot : https://ibb.co/svpzj6MW)

(For information, I also did a clean install with 128.x: it works...)

Comment 10

[Totoche2607]

(sorry, can you delette comment 7 & 8, my mistake when I edited)

Comment 11

[ajpeavler]

I've noticed this issue recently and it has caused problems for me. You should NEVER change a default setting which could affect users who depend on the feature's behavior to work as it has always done! Reminders which were scheduled to come up at a certain time were missed because I booted up my computer later in the day. Reminders which were snoozed disappeared completely. I have gone through my future events for the next several days and hope I have fixed all of the reminders so they will work again. I also had to review recent past events and found something that I should have done last week but missed the reminder. I missed some important reminders, but fortunately I discovered and fixed the issue before I missed anything that was critical.

I see that the setting was changed because people kept getting too many outdated reminders. Isn't this their own fault for not dismissing the reminders after they are finished with them? How many other people have missed important reminders because of this change and don't even know it yet? You could have added this setting without changing the default and causing people to miss important reminders!

Comment 12

[Totoche2607]

Hello,

I'm bringing this bug back up because it's really annoying on a daily basis...

As a reminder, this bug is intentional, since it resulted from an intentional modification (with very questionable arguments, by the way...).
The proof: an option has been implemented to work around it... but unfortunately it only solves half of the cases since it only works on events and not on tasks...

Thank you for taking this into account.

Translated with DeepL.com (free version)

Comment 14

[Francesco]

According to bug 1988288 comment 9 is't not a duplicate, so undoing the change. According to TB's QA (comment 6) it's not reproducible, so leaving it "unconfirmed".