bluez5: don't probe native backend presence
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, even though they do blocking calls on startup in previous pipewire versions too). Instead, select the backend once we have Bluez objects listed.
Loading
Please register or sign in to comment