ubuntuone-login crashed with AttributeError in from_token_and_callback()

[James Wylder]

Binary package hint: ubuntuone-client

Our story begins with me connecting my laptop (caprica) with Ubuntu One. This worked fine. I then tried a new installation of 10.04 on my desktop and it wouldn't connect to Ubuntu One. I would go to the System->Preferences->Ubuntu One and click manage account. This would take me to the web page, but not give me any ability to add my computer.

I then deleted my laptop from the web site and suddenly everything worked on the desktop (kobol).

Now back to adding my laptop and I see the same behavior that I saw on the desktop. After asking a question one the logs, I deleted the UbuntuOne token from the keychain. That brings us to the current state.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ubuntuone-client-gnome 1.1.91-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic i686
Architecture: i386
Date: Mon Apr 12 19:55:40 2010
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-login
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.6
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-login']
SourcePackage: ubuntuone-client
Title: ubuntuone-login crashed with AttributeError in from_token_and_callback()
UbuntuOneSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UserGroups: adm admin audio 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 #528117, 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.