New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.69] Somewhat broken, was the release pulled? #594
Comments
Just saw your bug report, and can confirm downgrading to 5.68 fixed my DS4 controller as well. |
Can you guys try with the latest, I suspect the following change should have it fixed: |
I have this issue as well with a DS4 and a DS5 controller. Can confirm that it's working again with latest commit |
Can confirm the issue, this is critical and Bluez 5.69.1 or 5.70 needs to be released, or else some devices are not working. Audio was working for me, but Dualshock 4 complete blackout. |
Commit fde32ff ("shared/gatt-client: Allow registering with NULL callback") added an early return to the notify_cb function when the current client's notify_list is empty which prevents sending confirmations to indications. Reported-by: Javier de San Pedro <dev.git@javispedro.com>
Can confirm the issue, too. Controller not pairing on 5.69; downgraded to 5.68 and everything is fine. |
@fionnb can you try with the latest just confirm it has been fixed upstream. |
Hello and thanks for the hard work I think I am also affected by this issue (openSUSE Tumbleweed, bluez 5.69, trying to connect to a Sony DualSense Controller (PS5 gamepad)) From this thread, I have the impression that a fix has already been implemented (apparently tested by @lilxandrias here), and I would like to know if you have a rough ETA for releasing a new version that includes the aforementioned fix. Unfortunately I am not an advanced enough user to manually compile / install and try out the current master branchon my system. Just for reference, here are more details about the issue I am experiencing (I am using GNOME settings to manage my BT devices):
relevant logs from systemd's
Sorry if it is too much noise but I would also like to mention @DimStar77 who I think is the maintainer for https://build.opensuse.org/package/show/openSUSE:Factory/bluez because it might be possible to release the fix for openSUSE as a patch somehow? |
Can confirm that the issue still exists in the latest version, and downgrading to 5.68 fixed it (Arch Linux btw). |
Hi, I am reporting Fedora 38 is impacted too. My DS4 knock off gamepads stopped working after the upgrade to 5.69. They worked flawlessly before that. Downgrade to 5.66 via |
I am using an official DS4 V2 controller on Nobara 38, and downgrading to 5.68-1 ( I had to downgrade on my EndeavourOS install too, from 5.69-1 to 5.68-1 BTW, this is not unique to Sony controllers. I was unable to connect my unofficial Wii Remote and unofficial Switch Pro Controller until I downgraded. Connecting bluetooth headphones and earbuds worked fine however. |
Can confirm. On a new install of Fedora 38 Plasma, my 8bitdo pro 2 bluetooth gave errors in pairing (in all 4 pairing modes). The downgrade to 5.66 was a quick "fix". |
Just reporting the Fedora 38 is now shipping bluez 5.70-1 but the version still does not work with my DS4s. I had to downgrade yet again. The last working version on Fedora 38 is still 5.66. |
I also tried 5.70 on Arch (Endeavour), still not working, had to downgrade 5.70-1 => 5.68-1 again. |
I can confirm the issue is not fixed by version 5.70. I still cannot connect a DS4 controller. |
Still having this problem on 5.70, controller works properly after downgrading to 5.68. Errors are: |
Perhaps it is related to #614? |
Looks like that's already fixed, but not released yet, so you can also switch to bluez-git package from AUR and it should also work. |
I will check with @holtmann if we can make a new release. |
I was about to make a formal issue report against 5.69, but it appears that no such release exists yet? I was experiencing issues with both my Xbox Series X|S Controller and a DualShock 4 Controller, where they would either randomly disconnect, or fail to connect properly in the first place. Reverting to 5.68 fixed the problem.
The text was updated successfully, but these errors were encountered: