Skip to content

bluez5: don't probe native backend presence

P V requested to merge pvir/pipewire:bluez5-delay-hfp into master

Don't do a blocking probe of native backend presence, because it may trigger DBus activation for Bluez. If the DBus activation fails, it ends up blocking until timeout.

ofono/hsphfpd usually don't have DBus activation configured, so they fail instantly (which is why this problem was not encountered in previous pipewire versions, which also do blocking DBus calls on startup).

Instead, select the backend once we have Bluez objects listed.

Fixes #1644 (closed)

Merge request reports