ubuntuone-launch crashed with ImportError in <module>()

Bug #626531 reported by archimonde
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubuntuone-client

ubuntuone-launch crashed with ImportError in <module>()

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: ubuntuone-client 1.3.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Mon Aug 30 00:00:06 2010
ExecutablePath: /usr/bin/ubuntuone-launch
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ubuntuone-launch
ProcCwd: /home/archimonde
ProcEnviron:
 LANGUAGE=en
 LANG=en_US.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/ubuntuone-launch']
SourcePackage: ubuntuone-client
Title: ubuntuone-launch crashed with ImportError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/ubuntuone-launch", line 38, in <module>
     from ubuntuone.syncdaemon.tools import SyncDaemonTool, is_running
 ImportError: No module named syncdaemon.tools
UbuntuOneSyncdaemonExceptionsLog: 2010-08-23 00:57:35,598 - ubuntuone.SyncDaemon.Main - ERROR - Local rescan finished with error: Traceback (failure with no frames): <type 'exceptions.UnicodeDecodeError'>: 'ascii' codec can't decode byte 0xc3 in position 18: ordinal not in range(128)
UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
archimonde (archimonde2001) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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 #624769, 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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.