How does D-Bus handle multiple interfaces on a single object path?

D-Bus deliberately separates "where" from "what": an object path identifies a single object, but that object can implement several interfaces simultaneously, each contributing its own set of methods, signals, and properties to that same address.

Every incoming method call specifies both the object path and the interface it's targeting, so the service's dispatch logic can route the call to the correct handler even when multiple interfaces on the same path define methods with the same name. A typical object, for example a NetworkManager device, might implement a device-specific interface alongside the standard org.freedesktop.DBus.Properties, org.freedesktop.DBus.Introspectable, and possibly org.freedesktop.DBus.Peer interfaces all at once, each independently addressable.

Introspection reflects this directly: the XML returned by Introspect() for a given object path lists each implemented interface as a separate <interface> element with its own methods, signals, and properties nested underneath, so a client can see the full set an object supports in one query.