Clicking on "Connect" in nautilus does nothing; files have not synced recently

[Andrew Morrison]

Binary package hint: ubuntuone-client

My files on Ubuntu One have not synced for a few days. The cloud icon in the tray indicates that files are up to date, but going to the website confirms they are not. Clicking on the "Connect" button in the nautilus window does nothing. Stopping the applet in the tray and restarting it also does not seem to fix anything.

ProblemType: Bug
.home.morris..cache.ubuntuone.log.oauth.login.log:
 Starting Ubuntu One client version 1.0.2
 Starting Ubuntu One client version 1.0.2
 Starting Ubuntu One client version 1.0.2
 Starting Ubuntu One client version 1.0.2
 Starting Ubuntu One client version 1.0.2
.home.morris..cache.ubuntuone.log.syncdaemon.exceptions.log: 2010-01-24 21:25:56,634 - ubuntuone.SyncDaemon.ActionQueue - ERROR - MakeDir share:'' node:'4fd287c4-e1e2-4017-b783-b5d87bfdefc5' MakeDir(marker="'4fd287c4-e1e2-4017-b783-b5d87bfdefc5'", parent_id="'fbf706f1-61f5-42b2-9153-93b1960a9056'", share_id="''", name="u'untitled folder'") failure Connection to the other side was lost in a non-clean fashion.
.home.morris..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = False
 connect = 0
 show_applet = 0
 bookmarked = True
Architecture: i386
Date: Fri Feb 5 06:26:17 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: fglrx
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-17-generic i686

[Dan Buhrman (dan-buhrman)]

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 474583, 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.