The rejected replies come from PipeWire's bluez5 SPA plugin, which WirePlumber loads (Ubuntu binary package libspa-0.2-bluetooth, source package pipewire), not from WirePlumber's own code.
BlueZ calls MediaEndpoint1.Release(), MediaEndpoint1.ClearConfiguration() and Profile1.Release() with NO_REPLY_EXPECTED set. The plugin replies anyway (a NotImplemented error, or an empty method return for ClearConfiguration), the bus has no pending call to match that reply against, and dbus-daemon rejects and logs it. BlueZ releases every registered endpoint when an adapter goes away or bluetoothd stops, hence one line per endpoint each time. Fixed upstream in master on 2026-10-01, not in a release yet: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/702a11de5b6bd48dcd358d000588dfa1618174c9 (MR https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/3032) It skips the reply when no reply is expected, as PulseAudio has done since 2018 (commit df79abe754a6). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2002182 Title: wireplumber initiates not implemented dbus message on bluez To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2002182/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
