| Summary: | [Bluetooth - Bluedevil] 3rd party DS4 Controller disconnects immediately after connecting | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | souravsm47 |
| Component: | Bluetooth in general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kdedev |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | bluetoothctl & journal logs | ||
|
Description
souravsm47
2025-08-24 12:00:10 UTC
Searchable bluetoothctl logs # bluetoothctl logs [bluetoothctl]> pair 59:22:5A:9A:2C:91 Attempting to pair with 59:22:5A:9A:2C:91 [CHG] Device 59:22:5A:9A:2C:91 Connected: yes [CHG] Device 59:22:5A:9A:2C:91 Bonded: yes [CHG] Device 59:22:5A:9A:2C:91 WakeAllowed: yes [CHG] Device 59:22:5A:9A:2C:91 ServicesResolved: yes [CHG] Device 59:22:5A:9A:2C:91 Paired: yes Pairing successful [CHG] Device 59:22:5A:9A:2C:91 ServicesResolved: no [SIGNAL] org.bluez.Device1.Disconnected org.bluez.Reason.Local Connection terminated by local host [CHG] Device 59:22:5A:9A:2C:91 Connected: no These indicate the problem is not in KDE Plasma, but in the underlying bluez code or in the kernel. Our code is only responsible for turning Bluetooth on or off, and manually connecting to devices; if devices stay connected or disconnect is determined by something deeper in the Bluetooth stack, in bluez or the kernel. I would recommend you follow up at [https://github.com/bluez/bluez/issues](https://github.com/bluez/bluez/issues). Thanks! Sorry, my bad. My controller is connecting with bluetoothctl. # bluetoothctl logs [bluetoothctl]> scan on SetDiscoveryFilter success Discovery started [CHG] Controller DC:F5:05:C1:E4:76 Discovering: yes [NEW] Device 59:22:5A:9A:2C:91 Wireless Controller [bluetoothctl]> pair 59:22:5A:9A:2C:91 Attempting to pair with 59:22:5A:9A:2C:91 [CHG] Device 59:22:5A:9A:2C:91 Connected: yes [CHG] Device 59:22:5A:9A:2C:91 Bonded: yes [CHG] Device 59:22:5A:9A:2C:91 WakeAllowed: yes [CHG] Device 59:22:5A:9A:2C:91 ServicesResolved: yes [CHG] Device 59:22:5A:9A:2C:91 Paired: yes Pairing successful [CHG] Device 59:22:5A:9A:2C:91 ServicesResolved: no [SIGNAL] org.bluez.Device1.Disconnected org.bluez.Reason.Local Connection terminated by local host [CHG] Device 59:22:5A:9A:2C:91 Connected: no [bluetoothctl]> connect 59:22:5A:9A:2C:91 Attempting to connect to 59:22:5A:9A:2C:91 [CHG] Device 59:22:5A:9A:2C:91 Connected: yes Connection successful [CHG] Device 59:22:5A:9A:2C:91 ServicesResolved: yes It is just not connecting using KDE settings UI. Idk what it is called, bluedevil maybe. Also, it used to work in KDE Plasma till whatever KDE version Fedora 38 LIVE used & after that it stopped working. It's a newly introduced bug, I think. Sorry again, it is working on KDE settings too, just a bit differently from earlier. Till Fedora 38 KDE: - Turn ON pairing mode in Controller. - Pair the Controller in KDE settings. The Controller will connect. After Fedora 38: - Turn ON pairing mode in Controller. - Pair the Controller in KDE settings. The Controller will get paired but will disconnect immediately afterwards. - DO NOT unpair the Controller in KDE settings. - Turn ON paring mode in Controller again. - Click the connect button in KDE settings. The Controller will connect. Quick connect has never worked & is still not working; neither with bluetoothctl, nor with KDE settings. |