ubuntuone-syncdaemon crashed with TypeError in __init__(): must be an interface

[chris koukas]

Binary package hint: ubuntuone-client

ubuntu crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
CheckboxSubmission: 4d3d4de1657ca7d73df244bb0082c8dd
CheckboxSystem: 25020ff6958bf4d49692136597cb229d
Date: Thu Feb 24 12:27:33 2011
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=el_GR:en
 LANG=el_GR.UTF-8
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-syncdaemon']
SourcePackage: ubuntuone-client
Title: ubuntuone-syncdaemon crashed with TypeError in __init__(): must be an interface
UbuntuOneOAuthLoginLog: 2010-04-19 16:28:58,990:990.930080414 ubuntuone-login Starting Ubuntu One login manager version 1.2.0
UbuntuOnePreferencesLog:
 2010-04-19 16:28:54,849 - ubuntuone-preferences - DEBUG - starting
 2010-04-19 16:29:01,834 - 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'))
UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 on = True
 read_limit = 2097152
 write_limit = 2097152
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 #724101, 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.