Clients are not notified about published files

Bug #788073 reported by Jo-Erlend Schinstad on 2011-05-25
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Undecided
Ubuntu One Client Engineering team
Ubuntu One Servers
Undecided
Ubuntu One Foundations+ team
Ubuntu One storage protocol
Undecided
Ubuntu One Foundations+ team
ubuntuone-client (Ubuntu)
Undecided
Ubuntu One Client Engineering team

Bug Description

Binary package hint: ubuntuone-client

Nautilus doesn't seem to be notified when you publish a file from the web or another computer. This means you have to click Publish on a file that is published in order to unpublish it.

Steps to reproduce:

1) Place a file in your Ubuntu One folder and make sure it's synchronized.
2) Open your Ubuntu One webpage to view your files: https://one.ubuntu.com/files/
3) Publish the file you just created.
4) Go back to Nautilus, right click the file and try to unpublish it.
5) Notice that the Ubuntu One menu of Nautilus only shows the possibility to publish the file, even though it is published.
6) Publish the (already published) file from Nautilus.
7) You're now notified that the file has been published, even though it already was.
8) Right click the file and observe that you can now unpublish the file from Nautilus.

I can see no easy way of determining whether a file has been published or not. If you want to make sure a file is not published, you either need to publish it and then unpublish it, or do it from the Ubuntu One website. This is very confusing behaviour. Connected Ubuntu One clients needs to be notified of these kinds of changes and act accordingly. I also think it should be much easier to see if a file has been published.

Changed in ubuntuone-client (Ubuntu):
assignee: nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+)
Changed in ubuntuone-client:
assignee: nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+)
summary: - Ubuntu One-menu in Nautilus is not properly synched.
+ Ubuntu One in Nautilus is not properly synched regarding published files
tags: added: desktop+ u1-nautilus
dobey (dobey) wrote :

This is a pretty invasive issue to fix. The problem is that published files information is not transmitted through the storage protocol. It is all done via a REST API. This means there is no way for the server to notify clients when files are published or unpublished on the web server. In order to fix, we'd need to add the necessary bits to the ubuntuone-storage-protocol, fix the server to notify via protocol, and fix the client to use the protocol for published files. Doing this would also fix several related bugs as well.

summary: - Ubuntu One in Nautilus is not properly synched regarding published files
+ Clients are not notified about published files
John O'Brien (jdobrien) on 2011-06-03
Changed in ubuntuone-servers:
assignee: nobody → Ubuntu One Foundations+ team (ubuntuone-foundations+)
Changed in ubuntuone-storage-protocol:
assignee: nobody → Ubuntu One Foundations+ team (ubuntuone-foundations+)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntuone-client (Ubuntu):
status: New → Confirmed
John Pugh (jpugh) wrote :

Sounds as if this is something that *should* be fixed as it's a usability issue. All clients *should* be notified of any change to the file no matter what the change.

I believe this is one of the issues behind the "a file is no longer published" bug #1193274

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers