Bug 2247548

Summary:	Unable to connect Dualshock4 v2 via Bluetooth (immediately disconnects after pairing)
Product:	[Fedora] Fedora	Reporter:	Mateus Rodrigues Costa <mateusrodcosta>
Component:	bluez	Assignee:	Gopal krishna tiwari <gopalkrishna.tiwari>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	38	CC:	dwmw2, gabeklav, gopalkrishna.tiwari, kparal, pbrobinson, spacewar
Target Milestone:	---	Keywords:	CommonBugs, Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	https://discussion.fedoraproject.org/t/94962
Fixed In Version:	bluez-5.70-3.fc39 bluez-5.70-5.fc39 bluez-5.70-5.fc38	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-12-09 02:40:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mateus Rodrigues Costa 2023-11-01 22:17:19 UTC

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
```

Comment 1 Mateus Rodrigues Costa 2023-11-01 22:32:46 UTC

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.

Comment 2 Mateus Rodrigues Costa 2023-11-02 15:35:47 UTC

Marking with CommonBugs so it can be a Proposed Common Issue on Fedora Discussion.

Comment 3 Mateus Rodrigues Costa 2023-11-09 18:59:12 UTC

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)

Comment 4 Fedora Update System 2023-11-19 14:10:31 UTC

FEDORA-2023-113a1e5fcd has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-113a1e5fcd

Comment 5 Fedora Update System 2023-11-20 02:02:37 UTC

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.

Comment 6 Fedora Update System 2023-11-21 02:49:19 UTC

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.

Comment 7 Kamil Páral 2023-11-21 13:30:06 UTC

Peter, can you please release the fix for F38 as well? Thanks.

Comment 8 Fedora Update System 2023-12-07 13:41:32 UTC

FEDORA-2023-26a02512e1 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-26a02512e1

Comment 9 Fedora Update System 2023-12-07 13:41:34 UTC

FEDORA-2023-6a3fe615d3 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6a3fe615d3

Comment 10 Fedora Update System 2023-12-08 01:32:37 UTC

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.

Comment 11 Fedora Update System 2023-12-08 02:38:09 UTC

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.

Comment 12 Fedora Update System 2023-12-09 02:40:57 UTC

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.

Comment 13 Fedora Update System 2023-12-11 01:28:23 UTC

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.

Comment 14 gabeklav 2024-05-03 02:01:01 UTC

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.