Created attachment 175391 [details]
Proof of succesful connection using bluetoothctl

Output of `journalctl` when adding the device:
```
Oct 30 21:47:32 fedora systemd[2032]: Started app-org.kde.bluedevilwizard@90213d2e493243eeab903e64174dc448.service - Add Bluetooth Device - Add Bluetooth Device.
Oct 30 21:47:32 fedora plasmashell[2439]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Oct 30 21:48:05 fedora bluedevil-wizard[74683]: kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
```

In contrast, output when adding through `bluetoothctl`:
```
Oct 30 21:49:28 fedora kernel: input: WH-1000XM5 (AVRCP) as /devices/virtual/input/input39
Oct 30 21:49:28 fedora systemd-logind[1376]: Watching system buttons on /dev/input/event27 (WH-1000XM5 (AVRCP))
Oct 30 21:49:28 fedora wireplumber[2132]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0
Oct 30 21:49:28 fedora kernel: hid-sensor-hub 0005:054C:0DF0.000C: unknown main item tag 0x0
Oct 30 21:49:28 fedora kernel: hid-sensor-hub 0005:054C:0DF0.000C: hidraw10: BLUETOOTH HID v2.31 Device [WH-1000XM5] on 10:6f:d9:dc:d8:c2
Oct 30 21:49:28 fedora flatpak[3133]: [21:49:28.991] [DBG] PwPipelineManager::on_registry_global: Audio/Source 83 bluez_input.88:C9:E8:25:5B:A1 with serial 3499 has been added
Oct 30 21:49:28 fedora flatpak[3133]: [21:49:28.992] [DBG] PwPipelineManager::on_registry_global: Audio/Sink 88 bluez_output.88_C9_E8_25_5B_A1.1 with serial 3501 has been added
Oct 30 21:49:28 fedora flatpak[3133]: [21:49:28.995] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: device bluez_card.88_C9_E8_25_5B_A1 has changed its output route to: headset-output
Oct 30 21:49:29 fedora flatpak[3133]: [21:49:29.017] [DBG] PwPipelineManager::on_metadata_property: new metadata property: 0, default.audio.sink, Spa:String:JSON, {"name":"bluez_output.88_C9_E8_25_5B_A1.1"}
Oct 30 21:49:29 fedora flatpak[3133]: [21:49:29.017] [DBG] PwPipelineManager::on_metadata_property: new metadata property: 0, default.audio.source, Spa:String:JSON, {"name":"bluez_input.88:C9:E8:25:5B:A1"}
Oct 30 21:49:29 fedora flatpak[3133]: [21:49:29.017] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: new default output sink: bluez_output.88_C9_E8_25_5B_A1.1
Oct 30 21:49:29 fedora pipewire[2131]: mod.client-node: detected old client version 5
Oct 30 21:49:29 fedora flatpak[3133]: [21:49:29.019] [DBG] PwBasePlugin::connect_to_pw: @PwJamesDspPlugin: JamesDsp successfully connected to PipeWire graph
Oct 30 21:49:29 fedora flatpak[3133]: [21:49:29.020] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: output device has changed to: bluez_card.88_C9_E8_25_5B_A1 via route headset-output
Oct 30 21:49:30 fedora plasmashell[2439]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Oct 30 21:49:39 fedora flatpak[3133]: [21:49:39.322] [DBG] FilterContainer::on_link_changed::<lambda>: No app linked to our device wants to play. Unlinking our filters.
Oct 30 21:49:39 fedora flatpak[3133]: [21:49:39.322] [DBG] FilterContainer::disconnect_filters: disconnecting the JamesDsp filter from PipeWire
Oct 30 21:50:14 fedora bluetoothd[72766]: /org/bluez/hci0/dev_88_C9_E8_25_5B_A1/sep3/fd2: fd(43) ready
```

Then, disconnecting and reconnecting again:
```
Oct 30 21:50:52 fedora bluetoothd[72766]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.993] [DBG] PwPipelineManager::on_destroy_node_proxy: Audio/Source 83 bluez_input.88:C9:E8:25:5B:A1 has been removed
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.993] [DBG] PwPipelineManager::on_destroy_node_proxy: Audio/Sink 88 bluez_output.88_C9_E8_25_5B_A1.1 has been removed
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.993] [WRN] PwPipelineManager::on_core_error: Remote error res: No such file or directory
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.993] [WRN] PwPipelineManager::on_core_error: Remote error message: unknown resource 60 op:2
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.993] [WRN] PwPipelineManager::on_core_error: Remote error res: No such file or directory
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.993] [WRN] PwPipelineManager::on_core_error: Remote error message: unknown resource 60 op:2
Oct 30 21:50:52 fedora kded6[2361]: org.kde.pulseaudio: No object for name "bluez_input.88:C9:E8:25:5B:A1"
Oct 30 21:50:52 fedora kded6[2361]: org.kde.pulseaudio: No object for name "bluez_output.88_C9_E8_25_5B_A1.1"
Oct 30 21:50:52 fedora kded6[2361]: org.kde.pulseaudio: No object for name "bluez_input.88:C9:E8:25:5B:A1"
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.997] [DBG] PwPipelineManager::on_metadata_property: new metadata property: 0, default.audio.sink, Spa:String:JSON, {"name":"alsa_output.usb-Logitech_PRO_X_Wireless_Gaming_Headset-00.analog-stereo"}
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.997] [DBG] PwPipelineManager::on_metadata_property: new metadata property: 0, default.audio.source, Spa:String:JSON, {"name":"alsa_input.usb-Logitech_PRO_X_Wireless_Gaming_Headset-00.mono-fallback"}
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.997] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: new default output sink: alsa_output.usb-Logitech_PRO_X_Wireless_Gaming_Headset-00.analog-stereo
Oct 30 21:50:52 fedora pipewire[2131]: mod.client-node: detected old client version 5
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.998] [DBG] PwBasePlugin::connect_to_pw: @PwJamesDspPlugin: JamesDsp successfully connected to PipeWire graph
Oct 30 21:50:52 fedora flatpak[3133]: [21:50:52.999] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: output device has changed to: alsa_card.usb-Logitech_PRO_X_Wireless_Gaming_Headset-00 via route analog-output
Oct 30 21:50:53 fedora plasmashell[2439]: org.kde.pulseaudio: No object for name "bluez_input.88:C9:E8:25:5B:A1"
Oct 30 21:50:53 fedora plasmashell[2439]: org.kde.pulseaudio: No object for name "bluez_output.88_C9_E8_25_5B_A1.1"
Oct 30 21:50:53 fedora plasmashell[2439]: org.kde.pulseaudio: No object for name "bluez_input.88:C9:E8:25:5B:A1"
Oct 30 21:50:54 fedora plasmashell[2439]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Oct 30 21:51:03 fedora flatpak[3133]: [21:51:03.322] [DBG] FilterContainer::on_link_changed::<lambda>: No app linked to our device wants to play. Unlinking our filters.
Oct 30 21:51:03 fedora flatpak[3133]: [21:51:03.322] [DBG] FilterContainer::disconnect_filters: disconnecting the JamesDsp filter from PipeWire
```

Was something else paired to the Bluetooth device at the time you tried to pair this one to it, by any chance?

(In reply to Nate Graham from comment #3)
> Was something else paired to the Bluetooth device at the time you tried to
> pair this one to it, by any chance?

In my own machine there was an Xbox controller paired but turned off. In my friends machine there were no other devices paired at first, then we paired a keyboard to see if the issue was the receiver, but it connected successfully.

So the same thing happened whether there were other devices paired or not.

Thanks for the info. I'll let folks with more knowledge about Bluetooth take over from here.

This hasn't been corrected as of Plasma 6.3.2

I have exhibited this same issue on both an Ubuntu base and fedora base, and on different hardware devices using Intel and AMD. I am able to successfully pair different brands of mice/trackballs on both devices without issue using the wizard/gui. I have tried to pair two different brands of keyboards via the wizard, without success. Both devices are seen, the pairing is attempted, but eventually fails with the same messages presented in this original post. However if you look in your BT device list, the keyboard will be listed - BUT it won't connect. In my experience, when pairing a keyboard, the system will present you with 6 numbers you have to enter on the keyboard and hit <enter>. That exchange never happens in the wizard. The bluetoothctl doesn't appear to present the number challenge, but it does successfully pair the keyboards, and then the device will be visible in the BT GUI and is connected successfully.