Re: [Evolution] calendar timeout? -

[Pete Biggs <pete biggs org uk>]

> > Run evolution-calendar-factory in a terminal with something like
> >  CALDAV_DEBUG={all|message:body|message:header|message|items|attachme
> > nt
> > s} evolution-calendar-factory >& logfileMultiple options can be
> > specified as a comma-separated list.
>
> I tried:
> $ evolution-calendar-factory CALDAV_DEBUG=all
>
> and got
> evolution-calendar-factory: Befehl nicht gefunden.
> (command not found)

So find the executable and execute it using the full path.  The
location of the evolution-calendar-factory file is distro dependent -
for Fedora it's in /usr/libexec - in all likelihood it's somewhere odd
in Ubuntu. 

And you've got it the wrong way round.  The command should look
something like

$ CALDAV_DEBUG=all /usr/libexec/evolution-calendar-factory >& logfile

> But system monitor shows a process called "evolution-calendar-factory".

Kill that process before starting one from the command line - it won't
work if there's another one running.

> I don't understand that line:
> > CALDAV_DEBUG={all|message:body|message:header|message|items|attachmen
> > ts} evolution-calendar-factory >& logfile

All it's saying is that the CALDAV_DEBUG variable can have different
values depending on what you want it to report on. Just use 'all' it'll
produce lots of output, but it will contain, somewhere, the problem.

> How would a proper line read?

See above

P.