This message means couchdb-glib couldn't find the token for Desktopcouch in the keyring. So I guess this is a desktopcouch problem we've seen a few times, that either it doesn't start (could you test this by trying to run /usr/lib/desktopcouch/desktopcouch-service on a terminal and see if it shows up any error?) or even though it does start, it doesn't sync the tokens in the keyring, so couchdb-glib doesn't know how to authenticate at all.
This message means couchdb-glib couldn't find the token for Desktopcouch in the keyring. So I guess this is a desktopcouch problem we've seen a few times, that either it doesn't start (could you test this by trying to run /usr/lib/ desktopcouch/ desktopcouch- service on a terminal and see if it shows up any error?) or even though it does start, it doesn't sync the tokens in the keyring, so couchdb-glib doesn't know how to authenticate at all.
So, follow the instructions at the 'killing and restarting dc' section at http:// www.freedesktop .org/wiki/ Specifications/ desktopcouch/ Documentation/ Troubleshooting and let's see if it's that, but it really looks like it indeed is, since that message comes from here:
http:// git.gnome. org/browse/ evolution- couchdb/ tree/addressboo k/e-book- backend- couchdb. c#n1099
and the only way desktopcouch_ session_ new can fail is because of it not being able to contact desktopcouch or finding the tokens in the keyring:
http:// git.gnome. org/browse/ couchdb- glib/tree/ desktopcouch- glib/desktopcou ch-session. c#n57
So either desktopcouch is not installed or not being started correctly, or it's not writing the tokens to the keyring.