Date: Tue, 26 Apr 2011 10:06:58 +0100 From: David Woodhouse <dwmw2@infradead.org> To: Matthias Apitz <guru@unixarea.de> Cc: gnome@freebsd.org, evolution-list@gnome.org Subject: Re: [Evolution] evolution-2.32.1 (FreeBSD HEAD) && calendar not working Message-ID: <1303808818.6417.63.camel@macbook.infradead.org> In-Reply-To: <20110426063226.GA13844@sh4-5.1blu.de> References: <20110424160107.GA3824@tinyCurrent> <20110424160553.GA21295@sh4-5.1blu.de> <1303668410.6417.4.camel@macbook.infradead.org> <20110424181903.GA1129@tiny> <1303673639.6417.7.camel@macbook.infradead.org> <20110425142311.GA31595@sh4-5.1blu.de> <1303760086.6417.25.camel@macbook.infradead.org> <20110426063226.GA13844@sh4-5.1blu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2011-04-26 at 08:32 +0200, Matthias Apitz wrote: > > OK. So please run e-calendar-factory from the command line, preferably > > in gdb, and show *its* output when you reproduce the original problem. > > Just to make sure the procedure: do you want me to 1) start > e-calendar-factory in gdb and 2) start 'evolution -c mail' and 3) switch > in evolution to calendar function, correct? how evolution will make use > of the previous started e-calendar-factory? Evolution talks to e-calendar-factory over DBus. If there is a factory already running, it'll talk to the existing one. If there is *not* one already running, it gets started automatically by DBus activation. So you need to kill any existing e-calendar-factory process, then run a new one from a terminal so you can see its output (and debug it if it crashes). Then start Evolution, and it'll use your new factory. -- dwmw2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1303808818.6417.63.camel>