Open Bug 1611544 Opened 6 years ago Updated 3 years ago

Calendar/Lightning - Error when moving an item of an recurring event

Categories

(Calendar :: General, defect)

Lightning 68
x86_64
Linux
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: mail, Unassigned)

Details

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

Steps to reproduce:

  • Go to Lightning Calendar
  • Create a new recurring event - let's say a weekly meeting, starting today without end (forever)
  • Move one item of this series to another day, or edit one item of the recurring event (NOT the whole series), e.g. change the title and try to save

Actual results:

An error dialog occurs, saying:

MODIFICATION_FAILED
Status-Code: 2147500037
Server Replied with 400

Expected results:

The one item should be detached from the series and now be able to edit individually.

I already dug deeper into the problem, because I needed an fix/workaround. Problem is, that the new detached item seems to contain both DTEND and DURATION information, which will be rejected from radicale calendar server (more specific the VObject library which is used). I workarounded it, as ca be seed here:

https://github.com/Kozea/Radicale/issues/985

I think it is an Thunderbird/Lightning bug, because the validation message (which can unfortunately only seen on server) is correct in my opinion: "VEVENT components cannot contain both DTEND and DURATION".

Component: Untriaged → General
OS: Unspecified → Linux
Product: Thunderbird → Calendar
Hardware: Unspecified → x86_64
Version: 68 → Lightning 68

Same problem, I also "fixed" it via the Kozea/Radicale work around. My comment is basically useless, but I'm posting one because I clicked the vote button, was directed to the voting page for this bug, checked the vote box ... and nothing happened. No vote added. I just stayed on that page. FYI

Same problem, solution would be highly appreciated. Thanks in advance!

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.