Deleting UDF on one computer does not delete it from others.
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Ubuntu One Client | Status tracked in Trunk | |||||
Stable-1-4 |
Fix Released
|
High
|
Guillermo Gonzalez | |||
Trunk |
Fix Released
|
High
|
Guillermo Gonzalez | |||
ubuntuone-client (Ubuntu) |
Fix Released
|
High
|
Unassigned | |||
Maverick |
Fix Released
|
High
|
dobey |
Bug Description
I created a UDF ~/Documents on computer 1 using Nautilus (Synchronize with Ubuntu One)... On computer2 the client created a UDF and synchronized all the files. The UDF was visible on the web.
On computer 1, I deleted the UDF in Nautilus (Stop Synchronizing with Ubuntu One).
The UDF was deleted (based on the syncdaemon.log) and was no longer visible on the WEB.
On computer 2, the UDF still remained even after a couple of restarts. u1sdtool --list-folders shows the folder as a UDF.
----
TEST CASE:
Need 2 computers with the same Ubuntu One account
1. Computer 1 - Open ~/Home, right-click on ~/Documents and select "Ubuntu One > Synchronize This Folder"
2. Computer 2 - Ensure ~/Documents is now being synced by Ubuntu One ($ u1sdtool --list-folders)
3. Computer 1 - Right-click on ~/Documents and select "Ubuntu One > Stop Synchronizing This Folder"
4. Computer 2 - Open Applications > Accessories > Terminal and run: u1sdtool --list-folders
Result: Computer 2 shows "subscribed=True" for ~/Documents from the u1sdtool --list-folders command
Expected result: Computer 2 returns "No folders" from the u1sdtool --list-folders command
----
If I try to put something in the folder, there is an exception on the Upload (syncdaemon-
Related branches
- John O'Brien (community): Approve
- dobey (community): Approve
-
Diff: 102 lines (+81/-0)2 files modifiedtests/syncdaemon/test_vm.py (+77/-0)
ubuntuone/syncdaemon/volume_manager.py (+4/-0)
- Natalia Bidart (community): Approve
- John O'Brien (community): Approve
-
Diff: 96 lines (+75/-0)2 files modifiedtests/syncdaemon/test_vm.py (+71/-0)
ubuntuone/syncdaemon/volume_manager.py (+4/-0)
Changed in ubuntuone-client: | |
assignee: | nobody → Ubuntu One Foundations+ team (ubuntuone-foundations+) |
importance: | Undecided → High |
Changed in ubuntuone-client: | |
assignee: | Ubuntu One Foundations+ team (ubuntuone-foundations+) → Guillermo Gonzalez (verterok) |
status: | Confirmed → In Progress |
Changed in ubuntuone-client (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Ubuntu One Ops+ team (ubuntuone-ops+) |
tags: | added: foundations+ u1-maverick-sru |
Changed in ubuntuone-client (Ubuntu Maverick): | |
milestone: | none → maverick-updates |
Changed in ubuntuone-client: | |
status: | In Progress → Fix Committed |
Changed in ubuntuone-client (Ubuntu Maverick): | |
assignee: | nobody → Rodney Dawes (dobey) |
importance: | Undecided → High |
status: | New → In Progress |
description: | updated |
description: | updated |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
tags: | added: testcase |
Changed in ubuntuone-client (Ubuntu): | |
assignee: | Registry Administrators (registry) → nobody |
A workaround is to execute: u1sdtool --refresh-volumes on the computer 2.