ubuntuone-syncdaemon crashed with DBusException in call_blocking()

[Nielstest]

crashed after a quite normal start and login.
this keeps comming back to me and it is often preceeded by a crash in the clock/date/weather (2.30.2) applet in
the top gnome panel (2.30.2) stating that weather could not be retrieved due to possible connectivity problems.
and i never get a chance of a bug report with the weather app unless ubuntu one also crashes or empathy does the same.
Mind that my Avant windows navigator also have a weather app (0.4.1:onox) and it 'always' works.
so i dont actualy have a internet connection problem rather may have a logon secuence problem.
used to have automatic logon but that just ment that the keyring feat asked twice for password and often crashed on top
of the crashes i have now.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: ubuntuone-client 1.4.6-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-30.56-generic 2.6.35.13
Uname: Linux 2.6.35-30-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Sep 6 13:15:28 2011
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_DK.utf8
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-syncdaemon']
SourcePackage: ubuntuone-client
Title: ubuntuone-syncdaemon crashed with DBusException in call_blocking()
UbuntuOneSyncdaemonExceptionsLog:

UserGroups: adm admin cdrom dialout lpadmin mythtv 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 #683234, 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.