Ubuntu
desktopcouch package

desktopcouch-service crashed with PreconditionFailed in request(): ('file_exists', 'The database could not be created, the file already exists.')

Bug #747680 reported by Rodolfo Pereira on 2011-04-01

This bug report is a duplicate of: Bug #707321: desktopcouch-service crashed with PreconditionFailed in request(): ('file_exists', 'The database could not be created, the file already exists.'). Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: desktopcouch

Trying to use Ubuntu one

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: desktopcouch 1.0.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Fri Apr 1 16:22:34 2011
ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_US:en
LANG=en_US.UTF-8
PythonArgs: ['/usr/lib/desktopcouch/desktopcouch-service']
SourcePackage: desktopcouch
Title: desktopcouch-service crashed with PreconditionFailed in request(): ('file_exists', 'The database could not be created, the file already exists.')
UpgradeStatus: Upgraded to natty on 2011-04-01 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Rodolfo Pereira (phinpho) wrote on 2011-04-01:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-04-04: 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 #707321, 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.