ubuntuone-syncdaemon NoAccessToken exception when trying to connect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When I attempt to connect a machine running Precise to an existing Ubuntu One accoung from the Ubuntu One Control Panel, it consistently fails. I get the message "The process did not finish successfully" in the connect dialog followed by a "There was a problem while retrieving the cred" in the control panel window (presumably the message is cut off). The following appears in ~/.cache/
2012-01-02 13:53:46,113 - twisted - ERROR - Unhandled error in Deferred:
2012-01-02 13:53:46,117 - twisted - ERROR - Unhandled Error
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
current.result = callback(
File "/usr/lib/
_inlineCall
--- <exception caught here> ---
File "/usr/lib/
result = g.send(result)
File "/usr/lib/
raise NoAccessToken("got empty credentials.")
ubuntuone.
Despite this, the machine shows up in my devices list when viewed on another machine or via the web interface. I am not behind a proxy, and attempting to connect to the same account from another machine running Oneiric is successful.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubuntuone-client 2.99.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-7-generic x86_64
NonfreeKernelMo
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Tue Jan 3 13:14:28 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20111208)
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntuone-client
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 910163, so it 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. Feel free to continue to report any other bugs you may find.