sync login to Ubuntu One via tomboy failed

[nano1]

Binary package hint: ubuntuone-client

Ubuntu 9.10 starting sync between ONE and tomboy delivered the info that my client software is newer than the server version and therefore there is a conflict.

ProblemType: Bug
.home.patrick..cache.ubuntuone.log.oauth.login.log: Ubuntu-One Client Version 1.0.2 wird gestartet
.home.patrick..cache.ubuntuone.log.syncdaemon.exceptions.log: 2009-10-31 21:55:55,800 - ubuntuone.SyncDaemon.ActionQueue - ERROR - Capabilities query failed: The server doesn't have the requested capabilities
.home.patrick..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 show_applet = 1
 connected = True
 connect = 0
 bookmarked = True
Architecture: i386
CheckboxSubmission: 55334ef07a82c407b49631a47cfd2051
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
Date: Sat Oct 31 22:23:16 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: ubuntuone-client 1.0.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:17636): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:17636): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:17740): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:17793): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:17887): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

[Rodrigo Moya (rodrigo-moya)]

This error seems to have nothing to do with Tomboy syncing, but with the u1 client applet. So, did you see this when syncing Tomboy notes? And, did the tomboy notes get synced?

[Matt Griffin (mattgriffin)]

Try upgrading your client software from 1.0.2-0ubuntu1 to 1.0.2-0ubuntu2 by running Update Manager and restarting the software (or logging-out/in).