1693284 - Editing recurring event pops up discard/submit dialog, but neither work

Status: UNCONFIRMED

(Calendar :: Provider: CalDAV, defect)

Description

[Henrik Pauli]

Attachment: Editing a Feb 2, 2021 instance shows the March 20, 2020 date in the resync dialog

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:85.0) Gecko/20100101 Firefox/85.0

Steps to reproduce:

Thunderbird alerts me of missed events unless I explicitly turn that off in the Config Editor. This repeatedly pops up a window that offers me to dismiss these events, upon which, the dialog with "Discard my changes and reload" and "Submit my changes anyway" buttons will pop up — telling me that the calendar event changed on the server since whatever got cached in Calendar.

Neither of these buttons will allow me to go further.

The same thing will happen if I try to edit my attendance in recurring events.

The calendar provider we use is SOGo, if I understand it properly. I can fix them by going to the web interface of SOGo and mark these events as attended or whatever. It's just impossible to edit them from Thunderbird/Calendar/Lightning.

Incidentally, the "this event has changed on the server, Discard or Submit anyway" dialog lists the event's first/original date, so maybe the confusion in Calendar's head is that it isn't trying to edit the correct date instance of the recurring event?

Actual results:

Pressing the Discard button yields temporary relief from the nagging, but the reminders will come back soon enough, making general Thunderbird use annoying.

Pressing the Submit anyway button will not submit anyway.

Expected results:

Discard and reload should actually reload the item and make it possible to edit it. Submit anyway should actually successfully submit my changes.

The Discard/Submit dialog maybe shouldn't even pop up in the first place if/as there's nothing actually wrong with the event in question.

Comment 1

[Henrik Pauli]

This may be similar to bug 630203, but I'm not entirely sure if it depends on how old the event is, or if there's any migration of data involved.

Comment 2

[Henrik Pauli]

New information: Some of these non-dismissable events disappeared when I switched to TbSync + its CalDav provider

However, today's meeting got stuck regardless and that's when I noticed that this date it refers to (2020-03-18) is one with no instances of the recurring event. I think it might have been originally the start date of this recurring event, but I'm not sure.

Why that should result in being unable to edit just an instance is beyond me, but that's what we're looking at.

Comment 3

[quentin.denis]

I have the same issue using the "Provider for Google Calendar" addon. How can I help with more troubleshooting it?