ubuntuone-preferenes fails to start when network load is high
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
Incomplete
|
Undecided
|
Roman Yepishev |
Bug Description
Binary package hint: ubuntuone-client
I was reporting additional details about bug 600832 (network cap not respected) when I noticed that ubuntuone-
$ ubuntuone-
ERROR:dbus.
ERROR:ubuntuone
It seems this is only happening when lots of outgoing traffic is causing high >10s latency on incoming connections
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubuntuone-
ProcVersionSign
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Tue Dec 14 13:40:57 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: ubuntuone-client
UbuntuOneSyncda
2010-12-14 13:10:46,355 - dbus.proxies - ERROR - Introspect error on org.freedesktop
2010-12-14 13:10:46,367 - ubuntuone.
UbuntuOneUserSy
[bandwidth_
read_limit = 20480
write_limit = 10240
on = True
Hello,
Could you please check whether u1stool --connect works for you after a clean reboot.
If that results in DBus timeout error, could you please archive the logs from ~/.cache/ ubuntuone/ log and attach them to the bug report. Most likely the issue is caused by the huge number of metadata files in syncdaemon directory.
This happens because there is a less-than-optimal storage of metadata in versions prior to what is now in nightlies and Natty Narwhal. Basically that's bug LP:436612. Since you have a fairly large number of files in your Ubuntu One directory I believe you would like to try the nightlies PPA (please note that downgrade to older metadata storage is not possible).
If you are interested in testing the new improved metadata storage (which takes syncdaemon about a second or two to start) then please have a look at https:/ /launchpad. net/~ubuntuone/ +archive/ nightlies. Please note that the nightlies releases are only automatically tested and there is a possibility that not all features are working at all times.