On Sun, 2007-09-23 at 22:21 +0200, Patrick Ohly wrote:
Looking at the current libebook API documentation [1] I see a
backend-died signal prototype. I don't remember having seen that
before - was the signal or its documentation added recently?
I suppose I can call g_signal_connect(ebook,
On Sun, 2007-09-23 at 22:13 +0100, Ross Burton wrote:
On Sun, 2007-09-23 at 22:21 +0200, Patrick Ohly wrote:
I suppose I can call g_signal_connect(ebook, backend-died, mycallback,
NULL), then in mycallback print an error and abort the process, right?
Aborting the process is a very drastic
Hello,
SyncEvolution users have started to report that the syncevolution
process hangs, as far as I could tell from the reports while accessing
the Evolution Dataserver through libecal's or libebook's synchronous
functions (e.g. in e_book_get_contact()).
It then also happened to me randomly with
On Sun, 2007-09-23 at 22:21 +0200, Patrick Ohly wrote:
Looking at the current libebook API documentation [1] I see a
backend-died signal prototype. I don't remember having seen that
before - was the signal or its documentation added recently?
The documentation was likely added recently, the
