Ubuntu One not connecting

[waynemcl]

Binary package hint: ubuntuone-client

upgrade from 9.04. 64bit. I deleted the tmp and Ubuntu One dirs, and purged/re-installed. Hangs on "connecting". poor bandwidth at this location.

ProblemType: Bug
.home.waynemcl..cache.ubuntuone.log.oauth.login.log: Starting Ubuntu One client version 1.0.2
.home.waynemcl..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 49152
 write_limit = 49152
 on = True
.home.waynemcl..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = False
 connect = 0
 show_applet = 1
 bookmarked = True
Architecture: amd64
Date: Tue Nov 10 13:25:24 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:1988): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1988): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2049): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2009): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-appearance-properties:3654): Gdk-CRITICAL **: gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed

[Philip Fibiger (pfibiger)]

Hi Wayne,

I'm sorry to hear Ubuntu One isn't working properly for you. In order to help better determine what the problem might be, can you answer the following questions:

1) Are you using NetworkManager?
2) Are you behind a proxy server?
3) Can you report back what the following steps report?
    Quit the Ubuntu One client
    Applications->Accessories->Terminal, then run:
    ubuntuone-client-applet

Thanks,
Philip

[Natalia Bidart (nataliabidart)]

Hi Wayne,

this is a known problem and we have released a bugfix already. You can do the follow up in Bug #488413.