Ubuntu
lernid package

lernid crashed with ImportError in /usr/lib/pymodules/python2.7/desktopcouch/records/server.py: No module named application.server

Bug #737480 reported by Bicherele on 2011-03-18

This bug report is a duplicate of: Bug #727232: lernid crashed with ImportError in /usr/lib/pymodules/python2.7/desktopcouch/records/server.py: No module named application.server. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: lernid

Installed lernid from Software Center, rebooted and started program.
Failed import DesktopCouchDB application server.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: lernid 0.7
ProcVersionSignature: Ubuntu 2.6.38-7.35-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Fri Mar 18 12:42:55 2011
ExecutablePath: /usr/bin/lernid
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/lernid
ProcEnviron:
SHELL=/bin/bash
LANG=es_ES.UTF-8
LANGUAGE=es_ES:en
PythonArgs: ['/usr/bin/lernid']
SourcePackage: lernid
Title: lernid crashed with ImportError in /usr/lib/pymodules/python2.7/desktopcouch/records/server.py: No module named application.server
UpgradeStatus: Upgraded to natty on 2011-03-09 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Bicherele (bicherele) wrote on 2011-03-18:

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

Revision history for this message

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