GNOME Bugzilla – Bug 694019
ContainerUpdateIDs signal broken
Last modified: 2013-02-27 08:15:42 UTC
For some reason we now signalize <container-id>,0 for every change which isn't right. Might be the logic to set the container-update-id is wrong in http://git.gnome.org/browse/rygel/tree/src/librygel-server/rygel-content-directory.vala#n448 or we should only add them if containerUpdateId really changes.
I can confirm this. If I delete a picture from my ~/Pictures folder ( I'm using media export ) I get 6 Container Updates, including updates for my Music and my Root folder. All but one of the update signals specifies a ContainerUpdateID of 0.
Is there any case where ContainerUpdateID == 0 makes a valid use-case?
I don't think so. Containers can have a ContainerUpdateID property of 0 but I think evented values of this property will always be greater than 0.
Created attachment 237428 [details] [review] cleans up and fixes container update signal handling in content directory.
Created attachment 237431 [details] [review] cleans up and fixes container update signal handling in content directory. v2 I suppose that some code in MediaExport plugin needs to be fixed as well to avoid receiving updates from some music related container when picture is deleted.
Created attachment 237435 [details] [review] Fix ContainerUpdateIDs variable to hold unique ids.
Review of attachment 237435 [details] [review]: Good catch, that was broken for a long time apparently.
Review of attachment 237431 [details] [review]: Thanks