ubuntuone-syncdaemon crashed with ImportError in /usr/lib/pymodules/python2.7/ubuntuone-client/ubuntuone/syncdaemon/filesystem_manager.py: cannot import name move_to_trash

[jbeitler]

Binary package hint: ubuntuone-client

I was trying to update 11.04

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Apr 11 07:57:54 2011
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-syncdaemon']
SourcePackage: ubuntuone-client
Title: ubuntuone-syncdaemon crashed with ImportError in /usr/lib/pymodules/python2.7/ubuntuone-client/ubuntuone/syncdaemon/filesystem_manager.py: cannot import name move_to_trash
UbuntuOnePreferencesLog:
 2010-06-09 08:20:41,418 - ubuntuone-preferences - DEBUG - starting
 2010-06-09 08:20:41,648 - ubuntuone-preferences - DEBUG - got limits: dbus.Dictionary({dbus.String(u'download'): dbus.Int32(2097152), dbus.String(u'upload'): dbus.Int32(2097152)}, signature=dbus.Signature('si'))
 2010-06-09 08:21:37,728 - ubuntuone-preferences - DEBUG - starting
 2010-06-09 15:16:51,263 - ubuntuone-preferences - DEBUG - starting
UpgradeStatus: Upgraded to natty on 2011-04-11 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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