https://bugs.kde.org/show_bug.cgi?id=499217
Bug ID: 499217
Summary: Unable to pair Bluetooth controller from pair dialogue
(bluedevil-wizard)
Classification: Plasma
Product: plasmashell
Version: 6.2.5
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Bluetooth in general
Assignee: plasma-b...@kde.org
Reporter: s...@n.dragon-vi.be
Target Milestone: 1.0
SUMMARY
When trying to use the Bluetooth pairing dialogue (bluedevil-wizard) to pair a
DualSense controller, it fails to pair the device, leaving it in a state that
is unable to connect. Same issue doesn't happen when 'manually' using
`bluetoothctl`
STEPS TO REPRODUCE
1. From either the widget or the System settings enable Bluetooth
2. Select to pair a new device
3. Turn on the controller in pairing mode (in my case PS button + three lines
button)
4. Select the controller from the list and click to pair
OBSERVED RESULT
The controller will turn off mid-pairing, and the pairing window will show "The
setup of DualSense Wireless Controller has failed". The controller will appear
in the list of paired devices, but will be unable to be connected to (turning
on the controller it will still be in a "awaiting for connection" mode, and
trying to press the connect button in Plasma will result in a silent failure)
EXPECTED RESULT
Properly pair and connect the controller to the system and be able to
automatically reconnect to it whenever turned off and on again and Bluetooth is
enabled on the computer
SOFTWARE/OS VERSIONS
Operating System: CachyOS Linux
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.10-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
ADDITIONAL INFORMATION
The device is only unable to pair when using the dialogue, using `bluetoothctl`
in the terminal the pairing works fine and the device is able to automatically
connect to the computer whenever turned off and on again
The steps to connect trough `bluetoothctl` being:
```
$ bluetoothctl
[bluetooth]# Agent registered
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
...
[bluetooth]# trust 58:10:31:65:E4:FC
[bluetooth]# [CHG] Device 58:10:31:65:E4:FC Trusted: yes
[bluetooth]# Changing 58:10:31:65:E4:FC trust succeeded
[bluetooth]# [CHG] Device 58:10:31:65:E4:FC Class: 0x00000508 (1288)
[bluetooth]# [CHG] Device 58:10:31:65:E4:FC Icon: input-gaming
[bluetooth]# pair 58:10:31:65:E4:FC
Attempting to pair with 58:10:31:65:E4:FC
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC Connected: yes
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC Bonded: yes
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC WakeAllowed:
yes
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC
ServicesResolved: yes
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC Paired: yes
[DualSense Wireless Controller]# Pairing successful
[DualSense Wireless Controller]#
```
(with the device being unpaired) When running `bluedevil-wizard` from the
terminal and going trough the pairing attempt, I get the following lines:
```
$ bluedevil-wizard
kf.bluezqt: PendingCall Error: "No discovery started"
kf.bluezqt: PendingCall Error: "br-connection-create-socket"
```
Also, if I keep `bluetoothctl` opened in a terminal, but don't touch it (using
only as a monitor for events) and use bluedevil-wizard for attempting to pair,
the following appear:
```
[bluetooth]# Agent registered
[bluetooth]# [CHG] Controller 8C:C6:81:96:17:9C Discovering: yes
[bluetooth]# [NEW] Device 58:10:31:65:E4:FC DualSense Wireless Controller
[bluetooth]# [CHG] Device 58:10:31:65:E4:FC RSSI is nil
[bluetooth]# [CHG] Controller 8C:C6:81:96:17:9C Discovering: no
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC Connected: yes
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC Bonded: yes
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC WakeAllowed:
yes
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC
ServicesResolved: yes
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC Paired: yes
[DualSense Wireless Controller]# [CHG] Device 58:10:31:65:E4:FC
ServicesResolved: no
[bluetooth]# [CHG] Device 58:10:31:65:E4:FC Connected: no
[bluetooth]# [CHG] Device 58:10:31:65:E4:FC Trusted: yes
```
When looking at logs from `journalctl` after attempting to pair from
bluedevil-wizard, the following appears:
```
jan 27 21:13:41 woods systemd[971]: Started Add Bluetooth Device - Add
Bluetooth Device.
...
jan 27 21:13:53 woods bluetoothd[727]: No matching connection for device
...
jan 27 21:13:58 woods bluetoothd[727]:
profiles/input/device.c:control_connect_cb() connect to 58:10:31:65:E4:FC: Host
is down (112)
jan 27 21:13:58 woods bluedevil-wizard[607123]: kf.bluezqt: PendingCall Error:
"br-connection-create-socket"
```
While when pairing successfully with `bluetoothctl` the following logs appear:
```
jan 27 21:16:41 woods kernel: playstation 0005:054C:0CE6.000F: unknown main
item tag 0x0
jan 27 21:16:41 woods kernel: playstation 0005:054C:0CE6.000F: hidraw1:
BLUETOOTH HID v1.00 Gamepad [DualSense Wireless Controller] on
8c:c6:81:96:17:9c
jan 27 21:16:41 woods kernel: input: DualSense Wireless Controller as
/devices/virtual/misc/uhid/0005:054C:0CE6.000F/input/input62
jan 27 21:16:41 woods kernel: input: DualSense Wireless Controller Motion
Sensors as /devices/virtual/misc/uhid/0005:054C:0CE6.000F/input/input63
jan 27 21:16:41 woods kernel: input: DualSense Wireless Controller Touchpad as
/devices/virtual/misc/uhid/0005:054C:0CE6.000F/input/input64
jan 27 21:16:41 woods kernel: playstation 0005:054C:0CE6.000F: Registered
DualSense controller hw_version=0x00000513 fw_version=0x01070008
```
This issue might be related to https://bugs.kde.org/show_bug.cgi?id=484847 that
was closed but am unsure for the lack of more logs and info there
The computer I'm using is a laptop (Legion 5i) with a built in wireless card
with Bluetooth functionality
--
You are receiving this mail because:
You are watching all bug changes.
