Could not connect to Evolution Exchange backend process

Bug #49142 reported by Christian Kirbach
6
Affects Status Importance Assigned to Milestone
evolution-exchange (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On startup an info window says

"Could not connect to Evolution Exchange backend process: No such file or directory"

I believe this was caused by the last Dapper updates - it used to work before.

I am using the Evolution exchange plugin.

Killling evolution-data-server-1.6 did not remedy.
Neither "bonobo-activation-sysconf --add-directory=/usr/lib/bonobo/servers"

Console messages:

----------
nazgul@dragonscale:~$ evolution
CalDAV Eplugin starting up ...

(evolution-2.6:4073): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one

(evolution-2.6:4073): e-utils-WARNING **: Plugin 'Bogofilter Ausschuss-Erweiterung' failed to load hook 'org.gnome.evolution.mail.junk:1.0'

----------

Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

similar to Bug #34199 but with the latest stable (Dapper)

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. The other bug you pointed mentions than running ximian-connector-setup-2.6 fixes the issue. Is that the case for you too? Do you remember from what version to what version did you update? Does it work better after running "evolution --force-shutdown" and restarting it?

Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

Running ximian-connector-setup-2.6 does not remedy.

evolution --force-shutdown solves the problem. Thanks.

Revision history for this message
John Vivirito (gnomefreak) wrote :

Christian is this still a problem or was it just a one time issue? Thank you for reporting this bug.

Changed in evolution-exchange:
status: Unconfirmed → Needs Info
Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

I can see this every now and then, but I do not know any way to trigger this on purpose.

Revision history for this message
John Vivirito (gnomefreak) wrote :

Make sure you are fully up-to-date and let me know if this is still an issue for you.

Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

Have rarely seen it in the last weeks.
Changing the active network interface using NetworkManager easily causes it.

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

I'm regularly suffering from this issue too.

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :

I'm runnig Edgy Eft using Evo 2.8.1. I'm still regularly getting that message.

Changed in evolution-exchange:
status: Needs Info → Confirmed
Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

I haven't seen this for quite some time.

Regarding me this has apparently been fixed upstream.

Revision history for this message
Brad Johnson (kkhww1902) wrote :

You would need to provide a backtrace of the evolution-exchange-storage process to determine what is really going on with this bug.

Changed in evolution-exchange:
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in evolution-exchange:
status: Incomplete → Invalid
Revision history for this message
oss_test_launchpad (oss-test-launchpad) wrote :

How would one do this backtrace thing?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.