Unchecking 'synchronize this folder' doesn't stop synchronization
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
Confirmed
|
Medium
|
Roman Yepishev |
Bug Description
Binary package hint: ubuntuone-client
Unchecking the "Synchronize this folder" checkbox in nautilus doesn't result in synchronization being stopped if you navigate away from the nautilus window before Ubuntu One is done unsynchronizing.
To reproduce:
1) Put a bunch of data (500MB in my case) in ~/Documents
2) Open a Nautilus window, navigate to the Documents folder
3) Check the "Synchronize this folder" checkbox inside the Nautilus window. Wait until synchronization completes, then verify that your files exist on one.ubuntu.com
4) Uncheck the 'Synchronize this folder' checkbox in Nautilus. A spinner will appear in the "Ubuntu One" area of the Nautilus window.
5) While the spinner is spinning, navigate away from the folder, e.g. by clicking the home directory link on the Nautilus side bar.
6) Navigate back to the Documents folder.
Actual results:
The 'Synchronize this folder' checkbox is checked.
Expected results:
The 'Synchronize this folder' checkbox is unchecked
This behavior is reproducible on my system.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubuntuone-client 1.4.5-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Fri Jan 14 14:19:18 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: ubuntuone-client
UbuntuOneSyncda
UbuntuOneUserSy
[bandwidth_
read_limit = 2097152
write_limit = 2097152
on = False
Changed in ubuntuone-client (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
This happens because the DeleteVolume is queued in the end of the metadata queue so it will actually remove the volume only after the complete synchronization of the metadata structure. Facundo, should DeleteVolume be somehow prioritized, jump to the head of the queue and drop all content/meta commands for the same volume id?