1852824 - freeze when creating event in CalDav calendar

Status: RESOLVED DUPLICATE of bug 1850732

(Calendar :: Provider: CalDAV, defect)

Description

[reg]

Attachment: thunderbird.out

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

Steps to reproduce:

I'm adding a CalDav calendar. The calendar is provded by hetzner.com.

Steps:

• "New Calendar…"
• "On the Network"
• enter url and credentials
• "Find Calendars"
• check the only found calendar
• "Subscribe"
• Add event in newly subscribed calendar

OS: Manjaro Linux
Thunderbird: 115.2.0 (64-bit)

Its perhaps worth mentioning that I used Thunderbird with this sort of calendar for several years without problems.

The Manjaro install is fresh, so is the linux user and the Thunderbird install. I can also reproduce the problem on Arch Linux and with other Hetzner calendars.

I'm attaching terminal output with calendar.debug.log and calendar.debug.log.verbose enabled.

Let me know if a strace could help. I can also provide access to the calendar.

Actual results:

The (empty) calendar is added without problems. Once I add a event with Thunderbird the application freezes up (a couple of seconds after clicking "Save and Close"). At that point Thunderbird isn't responsive to clicks or the keyboard and it uses 100% CPU (1/4 cores) according to htop. The event is actually added to the calendar and if I kill Thunderbird and restart it, it will freeze up the same way after a couple of seconds.

Expected results:

I would expect the CalDav calendar to be usable with Thunderbird. It works without problems with KOrganizer.

Comment 1

[Magnus Melin [:mkmelin]]

That's also Horde, so I suspect it's bug 1850732

Comment 2

[reg]

Interesting. Right, bug 1850732 and bug 1849540 seem related.

However, I can reproduce the problem with an empty CalDav calendar. When adding a event, Thunderbird freezes.

Maybe its relevant that I live in (and have Thunderbird configured with) time zone America/Los_Angeles (PDT, -0700) while the Horde server is in Germany and likely running with a different time zone.

Comment 3

[Magnus Melin [:mkmelin]]

Please check back once we fix bug 1850732 to see if it resolved the issue.