Christopher Schramm

😄 Anytime you like. I'm just trying to find a reasonable trade-off between keeping it to to date and not spamming the git history.

As far as I know, Fedora 36 uses PipeWire. Assuming that the headphones do not provide any HID service or anything, something, most probably PipeWire, must have handled the connection....

Assuming 2.3.1-1 is the respective Debian package, it ships the following polkit rules: https://salsa.debian.org/debian/blueman/-/blob/debian/2.3.1-1/debian/blueman.rules That means, you need to be in the `sudo` or `netdev` groups.

Did you restart blueman-applet with the new groups? Maybe try if `pkcheck --action-id org.blueman.network.setup --process $(pgrep blueman-applet)` gives you anything useful.

I would have expected a diagnostic message from `pkcheck`. Maybe try with `--allow-user-interaction`. As I already mentioned if 2.3.1-1 is the respective Debian package, authorization rules are set up as...

> Device will not pair. Is this the problem statement? I assume you're scanning, discovering some specific device and then use blueman to pair it but ... what? An error...

So the adapter is registered and seems to be scanning properly but it does not find any devices. Not sure if I can help here but I'd enable BlueZ debug...

To me the bluetoothd log looks like it fails to set up the streams between the audio server (presumably pulseaudio) and the device. The discover command times out. You should...

I don't think so and cannot find any reference. Otherwise, that would totally be a crucial difference between Linux Mint and the other Ubuntu 22.04 based systems. (Note: I interpret...

Oh wow. Surprising that this change is not mentioned in the release notes (while blueman is 🫣) but then it's rather clear that it's PipeWire that causes your problem. pulseaudio...