Ubuntu
desktopcouch package

desktopcouch-service crashed with ServerError in _request()

Bug #529841 reported by demancey on 2010-03-01

This bug report is a duplicate of: Bug #451767: desktopcouch-service crashed with ServerError in _request(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	desktopcouch (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: desktopcouch

10.04 LTS

desktopcouch:
  Installed: 0.6.1-0ubuntu1
  Candidate: 0.6.1-0ubuntu1
  Version table:
*** 0.6.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

for it to work

it crashed

ProblemType: Crash
Architecture: i386
Date: Sun Feb 28 21:56:23 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
InterpreterPath: /usr/bin/python2.6
Package: desktopcouch 0.6.1-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-14.20-generic
PythonArgs: ['/usr/lib/desktopcouch/desktopcouch-service']
SourcePackage: desktopcouch
Title: desktopcouch-service crashed with ServerError in _request()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

demancey (ldoss) wrote on 2010-03-01:

Traceback.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2010-03-01: This bug is a duplicate

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 #451767, 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.