Skip to content
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

Closed
kode54 opened this issue Sep 4, 2023 · 19 comments
Closed

[5.69] Somewhat broken, was the release pulled? #594

kode54 opened this issue Sep 4, 2023 · 19 comments

Comments

@kode54
Copy link

kode54 commented Sep 4, 2023

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.

@lavjamanxd
Copy link

Just saw your bug report, and can confirm downgrading to 5.68 fixed my DS4 controller as well.

@Vudentz
Copy link
Contributor

Vudentz commented Sep 6, 2023

Can you guys try with the latest, I suspect the following change should have it fixed:

670f0d0

@ComradeClaritux
Copy link

I have this issue as well with a DS4 and a DS5 controller. Can confirm that it's working again with latest commit

@lilxandrias
Copy link

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.

lilxandrias referenced this issue Sep 14, 2023
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>
@fionnb
Copy link

fionnb commented Sep 14, 2023

Can confirm the issue, too. Controller not pairing on 5.69; downgraded to 5.68 and everything is fine.

@Vudentz
Copy link
Contributor

Vudentz commented Sep 14, 2023

@fionnb can you try with the latest just confirm it has been fixed upstream.

@known-as-bmf
Copy link

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):

  • gamepad in pairing mode is detected properly
  • gamepad pairs properly
  • when connecting to the device (automatically after pairing or manually when the gamepad is already paired), the gamepad turns off by itself

relevant logs from systemd's bluetooth.service (I redacted my machine hostname and gamepad device id)

sept. 20 17:28:37 xxxxxxxxxx bluetoothd[1586]: profiles/input/server.c:connect_event_cb() Refusing input device connect: No such file or directory (2)
sept. 20 17:28:37 xxxxxxxxxx bluetoothd[1586]: profiles/input/server.c:confirm_event_cb() Refusing connection from XX:XX:XX:XX:XX:XX: unknown device

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?

@thanosngplus
Copy link

thanosngplus commented Sep 23, 2023

Can confirm that the issue still exists in the latest version, and downgrading to 5.68 fixed it (Arch Linux btw).

@kimec
Copy link

kimec commented Sep 24, 2023

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 dnf downgrade bluez\* "fixes" the issue.

@capitalistspz
Copy link

capitalistspz commented Sep 27, 2023

I am using an official DS4 V2 controller on Nobara 38, and downgrading to 5.68-1 (dnf downgrade bluez-5.68-1.fc38) fixed connections for me. (I was formerly on 5.69-2).

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.

@Natosphere
Copy link

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 dnf downgrade bluez\* "fixes" the issue.

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".

@Vudentz
Copy link
Contributor

Vudentz commented Sep 28, 2023

https://github.com/bluez/bluez/releases/tag/5.70

@kimec
Copy link

kimec commented Oct 27, 2023

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.

@fionnb
Copy link

fionnb commented Oct 29, 2023

I also tried 5.70 on Arch (Endeavour), still not working, had to downgrade 5.70-1 => 5.68-1 again.

@mikebm94
Copy link

I can confirm the issue is not fixed by version 5.70. I still cannot connect a DS4 controller.

@IsaacVaughn
Copy link

Still having this problem on 5.70, controller works properly after downgrading to 5.68. Errors are:
Nov 02 20:06:54 manjaro bluetoothd[2665913]: src/service.c:service_probe() input-hid profile probe failed for E4:17:D8:9D:A6:E7
Nov 02 20:08:21 manjaro bluetoothd[2665913]: profiles/input/server.c:connect_event_cb() Refusing input device connect: No such file or directory (2)
Nov 02 20:08:21 manjaro bluetoothd[2665913]: profiles/input/server.c:confirm_event_cb() Refusing connection from E4:17:D8:9D:A6:E7: unknown device
Nov 02 20:08:47 manjaro bluetoothd[2665913]: profiles/input/server.c:connect_event_cb() Refusing input device connect: No such file or directory (2)
Nov 02 20:08:47 manjaro bluetoothd[2665913]: profiles/input/server.c:confirm_event_cb() Refusing connection from E4:17:D8:9D:A6:E7: unknown device

@Vudentz
Copy link
Contributor

Vudentz commented Nov 3, 2023

Still having this problem on 5.70, controller works properly after downgrading to 5.68. Errors are: Nov 02 20:06:54 manjaro bluetoothd[2665913]: src/service.c:service_probe() input-hid profile probe failed for E4:17:D8:9D:A6:E7 Nov 02 20:08:21 manjaro bluetoothd[2665913]: profiles/input/server.c:connect_event_cb() Refusing input device connect: No such file or directory (2) Nov 02 20:08:21 manjaro bluetoothd[2665913]: profiles/input/server.c:confirm_event_cb() Refusing connection from E4:17:D8:9D:A6:E7: unknown device Nov 02 20:08:47 manjaro bluetoothd[2665913]: profiles/input/server.c:connect_event_cb() Refusing input device connect: No such file or directory (2) Nov 02 20:08:47 manjaro bluetoothd[2665913]: profiles/input/server.c:confirm_event_cb() Refusing connection from E4:17:D8:9D:A6:E7: unknown device

Perhaps it is related to #614?

@hawkeye116477
Copy link

Still having this problem on 5.70, controller works properly after downgrading to 5.68.

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.

@Vudentz
Copy link
Contributor

Vudentz commented Nov 4, 2023

I will check with @holtmann if we can make a new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests