gnome desktop freezes during Ubuntuone updating

[candtalan]

Binary package hint: ubuntuone-client

Ubuntu 9.10 is new on this PC. and U1 is now used, however frequently the desktop menus freeze while the cursor moves ok, but no mouse clicks nor keyboard get any responses. So the only consequence is a hard power off. This is the reason why the PC has been restarted several times, maybe that shows in the logs?

The PC is not being used for any other task but U1.
I am being plagued by u1conflict files also.
Not entirely sure it is U1 causing the probs. But it is a good coincidence, it keeps happening.

ProblemType: Bug
.home.candt..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 65536
 on = True
.home.candt..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = False
 connect = 0
 show_applet = 0
 bookmarked = True
Architecture: i386
Date: Tue Jan 5 22:36:27 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-16-generic i686
XsessionErrors:
 (gnome-settings-daemon:1475): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1507): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1513): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:1506): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24
 (nautilus:1757): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

[Guillermo Gonzalez (verterok)]

Hi,
there is a known bug in the throttling setting in this version of the ubuntuone syncdaemon.

Please quit the client, delete the file: ~/.config/ubuntuone/syncdaemon.conf and start the client again.

Thanks.

[Natalia Bidart (nataliabidart)]

Hi candtalan,

as Guillermo pointed out, we're aware of this issue, you can do the proper follow up in Bug #479204.

Regards, Natalia.