Ubuntu One crashes while updating files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubuntuone-client
This is related to Bug #502717 and Bug #502900. I don't know how to link this report to them.
Package version is 1.0.2 ubuntu2.
The sync daemon has been working for hours (>8) using 80-100% CPU, but almost no network traffic. And I went to sleep. When I came back the next morning, the "!" mark was on the icon and when I clicked on it crashed.
So, I am not sure the problem is not in the daemon instead, but have no other clue.
The initial subscription and upload of 500MB of files went alright a couple weeks ago. I have subscribed to the 50GB and now no way to update. I was trying to add/update 15 GB: is UbuntuOne unable to handle the load?
One last info: if memory serves there was a dialog box indicating progress of sync operations the first time. Now on all attemps I only have the icon and the system monitor to show the sync daemon is supposed to be working hard (80-90%).
Have reinstalled all UbuntuOne packages.
I have seen in another report that a version 1.0.3 was made available, but have not succeeded in getting to it.
Please; What should I do next?
ProblemType: Bug
.home.fg.
[ubuntuone]
connected = True
connect = 2
show_applet = 0
bookmarked = True
Architecture: i386
Date: Tue Jan 5 10:52:17 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitec
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ubuntuone-client
Tags: ubuntu-unr
Uname: Linux 2.6.31-16-generic i686
After 12 hours, directory structure has been created alright online in U1. But only a few files transfered. The U1 icon shows a cross. I loaded Nautilus and click connect. The icon shows a cloud for a few minutes, then a '!'.
I see in Bug #502717 that files with invalid utf-8 name could be the cause of the crash in my former report, and that this has been reported in Bug #368626.
Fair enough; but how do I solve this. Is there a tool to help me spot those file and correct their names?