Created attachment 188847 [details]
Video showing the bluetooth widget not updating earphones into "connected", and this working as expected with a controller

SUMMARY
When I connect a pair of earphones to my system, the earphones do not move into the "connected" section of bluetooth - despite being connected and working. This means they show as available, but cannot be disconnected.
This does not happen with every bluetooth device, as demonstrated with an Xbox Wireless controller

STEPS TO REPRODUCE
1. Turn on earphones
2. Let them auto connect to the device

OBSERVED RESULT
Earphones remain in the "Available" section (but display their battery life and work as expected).
The bluetooth icon does not update visually to say anything is connected.

EXPECTED RESULT
They move into the "connected" section, and allow you to use the disconnect button.
The bluetooth icon updates to say something is connected.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.5-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i9-9900K CPU @ 3.60GHz
Memory: 32 GiB of RAM (31.1 GiB usable)
Graphics Processor: AMD Radeon RX 6800

ADDITIONAL INFORMATION
I have shown a video of how this looks visually. The steps I took in the video:
- Start video
- Power on Earphones 
- Earphones connect and show their battery level, and are listed as an audio device - working as intended, but remain in the "available section"
- Clicking the connect button at this point does not do anything and times out (Journal log below)
- Powering on an Xbox wireless controller
- Xbox controller moves into "connected" and updates itself with the correct battery percentage.
- I disconnect the controller and it moves back into Available as expected
- The connect attempt fails on the earphones.
- I plug the earphones into a charger, forcing them to disconnect
- Doing so makes the battery level go away 


Interestingly, if the earphones are in 'searching' mode, for example I disconnect them from my phone and then move to my desktop, or if I re-pair the device, I can click "connect" and they will move into "connected" as expected. 
But if they connect straight away after being turned on, they remain in "available".

When first powering on and auto-connecting:

Jan 24 13:55:20 kathdesktop bluetoothd[1144]: Authorization request for non-connected device!?
Jan 24 13:55:20 kathdesktop wireplumber[2088]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+CHLD=?
Jan 24 13:55:20 kathdesktop wireplumber[2088]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0
Jan 24 13:55:20 kathdesktop wireplumber[2088]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+CGMI?
Jan 24 13:55:21 kathdesktop org_kde_powerdevil[2408]: Battery with UDI "/org/freedesktop/UPower/devices/headset_dev_61_9D_FC_B5_D6_33" was detected
Jan 24 13:55:21 kathdesktop bluetoothd[1144]: Authorization request for non-connected device!?
Jan 24 13:55:21 kathdesktop bluetoothd[1144]: Authorization request for non-connected device!?
Jan 24 13:55:21 kathdesktop kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257
Jan 24 13:55:21 kathdesktop kernel: input: PRM9689202 (AVRCP) as /devices/virtual/input/input56
Jan 24 13:55:21 kathdesktop systemd-logind[1196]: Watching system buttons on /dev/input/event30 (PRM9689202 (AVRCP))
Jan 24 13:55:21 kathdesktop kded6[2290]: No object for name "bluez_output.61_9D_FC_B5_D6_33.1"
Jan 24 13:55:21 kathdesktop plasmashell[2348]: No object for name "bluez_output.61_9D_FC_B5_D6_33.1"
Jan 24 13:55:23 kathdesktop bluetoothd[1144]: /org/bluez/hci0/dev_61_9D_FC_B5_D6_33/fd0: fd(44) ready

When clicking "connect" when they are already connected:

Jan 24 14:02:09 kathdesktop plasmashell[2348]: 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."


If you need any other information or logs, please let me know how to do so and I'll do the best I can. I have not had to debug bluetooth before