Bug 91283

Summary: GetManagedObjects spec not in sync what gdbus does
Product: dbus Reporter: Lennart Poettering <lennart>
Component: coreAssignee: D-Bus Maintainers <dbus>
Status: RESOLVED INVALID QA Contact: D-Bus Maintainers <dbus>
Severity: normal    
Priority: medium CC: dh.herrmann, zeuthen
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Lennart Poettering 2015-07-09 14:46:10 UTC 
The dbus spec currently says about GetManagedObjects():

    "The return value of this method is a dict whose keys are object paths. All returned object paths are children of the object path implementing this interface, i.e. their object paths start with the ObjectManager's object path plus '/'."

This seems to suggest that GetManagedObjects() does not return the object path of the object queried itself. However, that's not what gdbus apparently does, and I have the suspicion that the spec should be changed to do what gdbus does, rather than the other way round.

This came up in context of systemd's implementation of the api:

https://github.com/systemd/systemd/issues/525
Comment 1 Thiago Macieira 2015-07-10 01:20:59 UTC 
It makes sense to get the object itself. We should update the text to say that the reply includes itself *plus* those objects starting with the current's path followed by "/".
Comment 2 Simon McVittie 2015-07-13 10:05:34 UTC 
Spec patches welcome.

The ObjectManager interface was specified by GDBus developers, so I agree that GDBus' implementation is probably canonical here.
Comment 3 Lennart Poettering 2015-07-31 17:28:10 UTC 
As it appears GDBus isn't actually doing this, but bluez. The spec and gdbus are hence already in sync. Closing this bug hence.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.