>Did you test Ubuntu One out after rebooting? I deleted the pid file, rebooted and did
>not experience any couchdb problems until I tried to go into Ubuntu One. Then I got
>the same crashes as before. Problem not fixed on my system.
Yes, I tested Ubu One (last night) and it worked fine.
Here's the thing...
When I just rebooted my system (for probably the 5th time in approx 24 hr) I'm back to getting the desktopcouch-service can't be started warning.
However...
Ubu One is still working. Dittos for Gwibber, Pidgin, et cetera. Everything is working except, I'm back to getting the (supposed) desktopcouch-service cannot be started dialog.
>Did you test Ubuntu One out after rebooting? I deleted the pid file, rebooted and did
>not experience any couchdb problems until I tried to go into Ubuntu One. Then I got
>the same crashes as before. Problem not fixed on my system.
Yes, I tested Ubu One (last night) and it worked fine.
Here's the thing...
When I just rebooted my system (for probably the 5th time in approx 24 hr) I'm back to getting the desktopcouch- service can't be started warning.
However...
Ubu One is still working. Dittos for Gwibber, Pidgin, et cetera. Everything is working except, I'm back to getting the (supposed) desktopcouch- service cannot be started dialog.
Heh! This problem is a real corker, no?!?!?