This issue likely has been happening since Fedora 38 but I only notice it a few time and didn't pay much mind due to gaming less recently, but a while ago I switched to Fedora 39 and when I decided to game and the issue remained. Basically, whenever I try to connect the controller to my laptop via Bluetooth it will pair, connect for a bit and then disconnect. This issue is not on the controller side since I also own a PS4 and the controller works wirelessly correctly with it. The sincgle useful message I get when the issue appears is: ``` nov 01 19:03:58 centauro bluetoothd[1222]: src/service.c:service_probe() input-hid profile probe failed for <snip> ``` Where the <snip> replaces the device address. It seems for whatever bluez is failing to see that the controller is a crontoller. Reproducible: Always Steps to Reproduce: Try to pair the DualShock4 v2 via Gnome Settings' Bluetooth panel Actual Results: Controller connects and then quickly disconnects Expected Results: Controller should connect and keep connected Log message: ``` nov 01 19:03:58 centauro bluetoothd[1222]: src/service.c:service_probe() input-hid profile probe failed for <snip> ``` bluez version: ``` bluez-5.69-1.fc39.x86_64 bluez-cups-5.69-1.fc39.x86_64 bluez-libs-5.69-1.fc39.x86_64 bluez-obexd-5.69-1.fc39.x86_64 ```
Found upstream bug at https://github.com/bluez/bluez/issues/614. Apparently the choice are either applying https://github.com/bluez/bluez/commit/3a9c637010f8dc1ba3e8382abe01065761d4f5bb on top of 5.70 or downgrading to 5.68.
Marking with CommonBugs so it can be a Proposed Common Issue on Fedora Discussion.
bluez 5.70 made its way on the Fedora 39 stable release and the problem remains: ``` bluez-5.70-1.fc39.x86_64 bluez-cups-5.70-1.fc39.x86_64 bluez-libs-5.70-1.fc39.x86_64 bluez-obexd-5.70-1.fc39.x86_64 ``` Would it be possible to backport the patch mentioned above? (https://github.com/bluez/bluez/commit/3a9c637010f8dc1ba3e8382abe01065761d4f5bb)
FEDORA-2023-113a1e5fcd has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-113a1e5fcd
FEDORA-2023-113a1e5fcd has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-113a1e5fcd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-113a1e5fcd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-113a1e5fcd has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
Peter, can you please release the fix for F38 as well? Thanks.
FEDORA-2023-26a02512e1 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-26a02512e1
FEDORA-2023-6a3fe615d3 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6a3fe615d3
FEDORA-2023-6a3fe615d3 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6a3fe615d3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6a3fe615d3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-26a02512e1 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-26a02512e1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-26a02512e1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-6a3fe615d3 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-26a02512e1 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
The problem still persists for me on Fedora 40, as well as many people in this GitHub Issue thread https://github.com/bluez/bluez/issues/614 The bluez updates appear to have not fully fixed the issue.