

Can you maybe give us a ls -Al of /var/lib/radicale and /var/lib/radicale/collections to double check the permissions? I just looked at the systemd documentation and the service definition looks ok.
Can you maybe give us a ls -Al of /var/lib/radicale and /var/lib/radicale/collections to double check the permissions? I just looked at the systemd documentation and the service definition looks ok.
I suspect its got something to do with the systemd service definition. You may have to tweak the parameters under “optional security settings” to make it work. Or maybe you could start radicale manually from the command line, just for testing, and see if that works
I don’t know if you’re using debian but I encountered the same issue. The wiki has instructions to fix this (section create essential directories):
I’ve just set up Wireguard, so I can access my home network from everywhere, but the old laptop that I wanted to use as a server has just quit. So now I have to find a different machine
This is such a silly idea. One thing that many tech companies seem to forget nowadays: software needs to be predictable. If I subscribe to a channel, I expect the system to notify me about new uploads. If it doesn’t, people will assume that it doesn’t work. This is the reason why I’ve cancelled my YouTube Premium subscription: Youtube thinking it knows better than me.
I use k3b for ripping and kid3 for editing metadata
I also use Rhythmbox, the UI is clean and simple. Other music players either are too complicated (UI has too much clutter, play queues) or want to automatically import all audio files in my home directory into the library, which is annoying. But to be fair, I haven’t tried a lot of other players, because I’m happy using Rhythmbox.
That’s normal. On BIOS systems the stage 1 bootloader (which is what this command installs) is always i386, see https://wiki.archlinux.org/title/GRUB#Installation_2 .
What surprises me is that the installer runs in BIOS mode, because your system should be recent enough to use EFI. When you boot into the installer, you should make sure to select the boot entry that has EFI in its name. That might be the problem, but without seeing the output of grub-install, it’s hard to tell.