Re: [Evolution] CalDAV is readonly

On Tue, 2020-01-14 at 07:43 +0000, Krauß, Peter (SCC) via evolution-
list wrote:
I did indeed do several restarts (without success).

just to be clear, I didn't mean restart of the whole machine, but
restart of the calendar factory only, that is, of the
evolution-calendar-factory process.

You even do not need to kill the process to be restarted, just close
evolution, open terminal and execute there:

   $ /usr/libexec/evolution-calendar-factory -w

then wait for few seconds and only then start Evolution. Though I think
you captured the log from the initial email in a very similar way and
it still did not work, thus this won't work as well.

Maybe you can run DBus monitor and search what it passed around. You
might focus on "writable" and "Writable" (quotes for clarity only)
signals/properties. The command is:

   $ dbus-monitor

then I see for example this after I open a calendar which had not been
opened yet:

  signal time=1578997003.522247 sender=:1.181 -> destination=(null destination) serial=878 
path=/org/gnome/evolution/dataserver/Subprocess/6081/25; interface=org.freedesktop.DBus.Properties; 
  string "org.gnome.evolution.dataserver.Calendar"
  array [
     dict entry(
        string "Writable"
        variant             boolean true
  array [

followed by a method invocation response:

  method return time=1578997003.522745 sender=:1.181 -> destination=:1.226 serial=879 reply_serial=42
     array [
        string "alarm-email-address"
        string "''"
        string "cache-dir"
        string "writable"
        string "true"

this is how the backends notify the clients about their state, one of
them being writability. It's hard to recognize which calendar the
response belongs to, that why I'd try on one, which is not opened yet.
Note the dbus-monitor output will be very chatty, quite many things
sends something over D-Bus all the time, thus expect interleaved

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]