[SOLVED] Radicale CalDaV and Thunderbird client, All calendars are currently disabled

mfoley · 01-12-2024, 04:58 PM

Since upgrading to Radicale 3.1.8 on my Linux Slackware 15.0 server, I cannot connect to it properly from my Thunderbird 115.6.0 Linux client.

On Thunderbird, my calendar is marked with a triangle warning with an "ENABLE" button, but when I click "ENABLE" I get numerous "Unexpected status adding item to Mark's Calendar: 409" and a final "Could not perform playback operation add for item <item> Server Replied with 409" in the Error Console.

I've tried re-creating a new calendar, but on the dialog that says, "Please select the calendars you would like to subscribe to" the selected calendar checkbox is grayed out. The Error Console says, "No such JSWindowActor 'DevToolsFrame'", but not sure that's related to adding a new calendar.

Does anyone know what's going on with this?

allend · 01-12-2024, 11:36 PM

No problems for me when connecting from my Thunderbird 115.6.0 Linux client to my Slackware 15.0 server running Radicale 3.1.8.

A web search for the error "No such JSWindowActor 'DevToolsFrame'" does not show much, but seems to be associated with login errors. Perhaps check the logs in /var/log/httpd/ for clues.

bitfuzzy · 01-14-2024, 07:29 AM

Quote:

Originally Posted by mfoley

On Thunderbird, my calendar is marked with a triangle warning with an "ENABLE" button

Open the preferences for the problem calendar and look at the "Refresh Calendar" setting.
If it's set to "Manual" try changing it.

I had a similar issue a while back however I use ModDAV with Apache and haven't used Radicale so I don't know if the issue I had relates or not.

The issue started after a Thunderbird update and ended up being caused by the calendar's "refresh calendar" setting I was using at the time (Manual).
Changing it to Every 60 Minutes (5 min, 15 min, whatever) resolved my issues and I haven't had a problem since.

mfoley · 01-15-2024, 08:27 PM

I believe I've got this fixed. The upgrade to Radicale 3.1.8 has some important differences from my previous 2.1.11. The respective startup commands are:

Code:

# 2.1.11 :
su radicale --command "/usr/bin/radicale -d"

# 3.1.8 :
daemon -n radicale -u radicale -o local1.warning -e "HOME=/var/lib/radicale" -D /var/lib/radicale -- python3 -m radicale

The new version wanted a group named radicale so I had to change group ownership of all radical owned files from group caldav to group radicale. I changed the above as-installed command to:

Code:

daemon -n radicale -u radicale -o local1.warning -e "HOME=/home/radicale" -D /home/radicale -- python3 -m radicale

I kept my calendar info in /home/radicale, not /var/lib/radicale. I can't seem to find what the '-o local1.warning' does. My original config was:

Code:

[server]

hosts = 0.0.0.0:5232

pid = ~/pid

ssl = False

[encoding]

[auth]

type = htpasswd
htpasswd_filename = /etc/httpd/passwords
htpasswd_encryption = bcrypt

[rights]

type = none

[storage]

filesystem_folder = ~/collections

[headers]

I had to remove the "no longer supported" 'pid' option, and keep the 'filesystem_folder' option. One that took me a while to figure out was '[rights] type = None'. That worked on 2.1.11 and that spelling was in the config example. With 3.1.8 "none" must be lowercase. Otherwise Radicale fails to start. Sheesh!