Comment 11 for bug 544753

I have been trying to workaround this bug as a user, and the following are my posts from the Ubuntu Forums, I was asked to post my findings to Launchpad, hopefully this is the appropriate place to do so. If not, I will be happy to clean up any mess.

From http://ubuntuforums.org/showthread.php?p=9248847#post9248847 I am TyroneSlothrop in the thread.

Essentially, I did the following:

I issued the command: killall beam
I then removed the couchdb initialization file: rm ~/.config/desktop-couch/desktop-couchdb.ini
I then issued the following command: dbus-send --session --dest=org.desktopcouch.CouchDB --print-reply --type=method_call / org.desktopcouch.CouchDB.getPort
I then issued the command: xdg-open file:///home/USERNAME/.local/share/desktop-couch/couchdb.html

I was then presented with the Couch DB debugger, Futon. I was able to run the oauth, replication, security_validation, and conflicts under the Test Suite option.

After that, I could once again re-sync with Ubuntu One, I had entries for Desktop Couch in keyring. I was not able to start Gwibber, but when I tried I got a new message about a client not being present, not the original error message. I then was able to run Broadcast Preferences in Administration, and ticked the 'Start service at login', ran some updates, restarted, and gwibber is now running for me.

Not sure if what I did got it fixed, or if there was a fix in the updates, but hopefully this helps others with this issue.

Thinking about it now, I think that the format of the keyring entries got jiggered in the upgrade, but that is an amateurs speculation, your mileage may vary, as they say.

Cheers.