Comment 33 for bug 552227

Here's a more in-depth triage effort to try depending on how much manual manipulation you may have done to attempt to fix this issue. I broke couchdb pretty bad by manually purging things from it out of my home directory, not knowing it was a flat-database with a web front end.

The following steps should only be done if you think you've busted up desktopcouch in the process of trying to fix gwibber:

1) Completely purge gwibber
  -sudo apt-get purge gwibber

2) Completely purge desktop-couch
  -sudo apt-get purge desktopcouch

3) perform autoclean and autoremove to clean up all dependencies
  - sudo apt-get autoclean && sudo apt-get autoremove

4) ensure that ~/.local/share/desktop-couch is removed. if its not, just rename it so when you reinstall desktop-couch, it completely regenerates its database structure.

5) Click on Accessories then Passwords and Encryption Keys and under Passwords:login, remove the Gwibber-pref key.

6) Reinstall Desktop-Couch
  -sudo apt-get install desktopcouch

7) Reinstall gwibber
  - sudo apt-get install gwibber

8) There is a way to manually kick off the desktopcouch services in your active session, but I was unsuccessful in doing so, so right about here, I'd log out of your account and log back in. You dont have to reboot.

9) You should now be able to add y our facebook account using the steps above because there should be no pre-existing settings in desktopcouch's database as you have re-initialized it.

This app still doesn't feel "Ready for primetime" being this fragile, but when it does work, I will admit its pretty nice!