Ubuntu One no conecta

[pntkrtr]

La sincronización con tomboy es correcta, la máquina la he podido añadir a la lista de maquinas conectadas a través de la sincronización de tomboy, de otra forma no me ha sido posible, pero los contactos de evolution y los archivos no se sincronizan.
Si le doy a conectar no hace nada.

ProblemType: Bug
.home.pntkrtr..cache.ubuntuone.log.syncdaemon.exceptions.log:
 2009-10-26 00:22:02,024 - dbus.proxies - ERROR - Introspect error on org.freedesktop.NetworkManager:/org/freedesktop/NetworkManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
 2009-10-26 00:22:02,032 - ubuntuone.SyncDaemon.DBus - ERROR - Error while getting the NetworkManager state org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
.home.pntkrtr..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = True
 connect = 0
 show_applet = 1
 bookmarked = True
Architecture: i386
CrashDB: ubuntuone
Date: Mon Oct 26 00:22:32 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
ThirdParty: True
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:2277): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2277): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2324): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2365): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Joshua Hoover (joshuahoover)]

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