desktopcouch-service crashed with RuntimeError in run_couchdb()

[terryazthompson]

1) release 10.4 lts

2) not sure of the package responsible

3) i expected to have my running. I was scrolling down in firefox once, in other places the other 3 times it happened today. in all cases I expected the computer not to reboot.

4) My screen went blank, sound stopped and disk grinded for a few minutes, looked very close to reboot, may have been x restart, don't know enough to tell. After a while, a message comes up says that it will need to go into low graphics mode because it cannot detect my graphics card. click on use low graphics mode (white simple graphics menu) and it continues to on to restart.

NOTE: dell inspiron 1150, running 9.10 since october, never any problems happened 4 times first day I loaded 10.4

ProblemType: Crash
Architecture: i386
Date: Sun Mar 21 01:13:32 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.6
Package: desktopcouch 0.6.3-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
PythonArgs: ['/usr/lib/desktopcouch/desktopcouch-service']
SourcePackage: desktopcouch
Title: desktopcouch-service crashed with RuntimeError in run_couchdb()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[terryazthompson (terry-azthompson)]

please email me at <email address hidden> if you need any more information or testing.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #530541, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.