Closed Janik-Haag closed 11 months ago
I guess that we can drop the warning if you’re not doing any write operation (new, edit, import, etc).
It's complaining because the default calendar is mostly used for adding new events, which is a write action, and c3voc
is set to read only in your configuration.
I take it from that and your vdirsyncer configuration you're trying to use khal without any new/edit functionality?
If so, try without the default_calendar=c3voc
line.
I guess that we can drop the warning if you’re not doing any write operation (new, edit, import, etc).
It's not just complaining it's straight up crashing.
It's complaining because the default calendar is mostly used for adding new events, which is a write action, and
c3voc
is set to read only in your configuration.I take it from that and your vdirsyncer configuration you're trying to use khal without any new/edit functionality?
If so, try without the
default_calendar=c3voc
line.
Thanks that fixed it, I didn't quite know what to make of the error, closing this since it works now but some more verbose error message might be nice :D
Describe the bug A clear and concise description of what the bug is. I can't start khal because of the error: critical: default_calendar may not be read_only!
If applicable: Stack Trace Please copy the stack trace if khal crashes. No stacktrace
To Reproduce Steps to reproduce the behavior: I'm using this khal config:
and this vdirsyncer config:
after running:
the calendars are indeed not readonly, so I did
chmod -R 500 ~/.cal/
but that didn't solve it.Expected behavior A clear and concise description of what you expected to happen. Start khal/ikhal as expected
OS, version, khal version and how you installed it: