https://bugs.kde.org/show_bug.cgi?id=508671
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|REPORTED |RESOLVED CC| |[email protected] --- Comment #1 from TraceyC <[email protected]> --- 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! -- You are receiving this mail because: You are watching all bug changes.
