https://bugs.kde.org/show_bug.cgi?id=425941

--- Comment #3 from James Th <ja...@thornber.io> ---
what you say makes total sense! :)

So, I used buetoothctl, and this was the result:

luetoothctl
Agent registered
[NEW] Device 28:C1:3C:A2:91:02 Wireless Controller
[bluetooth]# scan on
Discovery started
[CHG] Controller D4:6D:6D:53:46:06 Discovering: yes
[bluetooth]# devices
Device 28:C1:3C:A2:91:02 Wireless Controller
[CHG] Device 28:C1:3C:A2:91:02 Trusted: yes
[bluetooth]# pair 28:C1:3C:A2:91:02
Attempting to pair with 28:C1:3C:A2:91:02
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[bluetooth]# 

So it must be failing earlier in the stack.  So I know this is no longer a KDE
issue, but do you have any ideas at all please?

Here's my output from: journalctl | grep Blue*

Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: Core ver 2.22
Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: HCI device and connection
manager initialized
Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: HCI socket layer
initialized
Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: L2CAP socket layer
initialized
Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: SCO socket layer
initialized
Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: hci0: Firmware revision
0.1 build 50 week 12 2019
Aug 29 16:54:24 yshtola.chilli.ai systemd[1]: Starting Bluetooth service...
Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Bluetooth daemon 5.54
Aug 29 16:54:24 yshtola.chilli.ai systemd[1]: Started Bluetooth service.
Aug 29 16:54:24 yshtola.chilli.ai systemd[1]: Reached target Bluetooth.
Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: BNEP (Ethernet Emulation)
ver 1.3
Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: BNEP filters: protocol
multicast
Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: BNEP socket layer
initialized
Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Bluetooth management
interface 1.17 initialized
Aug 29 16:54:37 yshtola.chilli.ai systemd[588]: Starting Bluetooth OBEX
service...
Aug 29 16:54:37 yshtola.chilli.ai systemd[588]: Started Bluetooth OBEX service.
Aug 29 16:54:37 yshtola.chilli.ai kernel: Bluetooth: RFCOMM TTY layer
initialized
Aug 29 16:54:37 yshtola.chilli.ai kernel: Bluetooth: RFCOMM socket layer
initialized
Aug 29 16:54:37 yshtola.chilli.ai kernel: Bluetooth: RFCOMM ver 1.11
Aug 29 16:54:37 yshtola.chilli.ai kded5[666]: bluedevil: Bluetooth operational
changed true

Here's what appears in systemctl status bluetooth:

Aug 29 16:54:24 yshtola.chilli.ai systemd[1]: Started Bluetooth service.
Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Starting SDP server
Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Bluetooth management
interface 1.17 initialized
Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: sixaxis: compatible device
connected: Wireless Controller (054C:09CC /sys/devices/pci0000:00/0000:00:14.0>
Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: sixaxis: setting up new
device
Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Authentication attempt
without agent
Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Add Device complete for
unknown device 28:C1:3C:A2:91:02
Aug 29 16:55:05 yshtola.chilli.ai bluetoothd[423]: sixaxis: compatible device
connected: Wireless Controller (054C:09CC /sys/devices/pci0000:00/0000:00:14.0>
Aug 29 16:55:05 yshtola.chilli.ai bluetoothd[423]: sixaxis: setting up new
device

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to