desktopcouch-service crashed with NameError in unpublish()

[Moahadeb]

Binary package hint: desktopcouch

lsb_release -rd;apt-cache policy desktopcouch
Description: Ubuntu maverick (development branch)
Release: 10.10
desktopcouch:
  Installed: 0.6.6-0ubuntu3
  Candidate: 0.6.6-0ubuntu3
  Version table:
 *** 0.6.6-0ubuntu3 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

don't know what should have happened just saw a red ! when the server was done booting.

start up crash.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: desktopcouch 0.6.6-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Sep 9 09:59:50 2010
ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
PythonArgs: ['/usr/lib/desktopcouch/desktopcouch-service']
SourcePackage: desktopcouch
Title: desktopcouch-service crashed with NameError in unpublish()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Moahadeb (cwesbrooks)]

I love Ubuntu, I started using windows 7 ultimate (what, you can fill in lol) it was clunky. I had some issues with it and desided to come back to the thing that I have used for so long now. I have used windows since 3.1, i have never felt that way about it!

Keep up the good work and thank you to all that help fix the bugs.

Carlos (old timer)

Using linux since redhat 3

[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 #625573, 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.