After upgrading to Fedora 44, Bluetooth devices no longer reconnect reliably after being powered off and on again.

This affects at least:
- Logitech MX Anywhere 3S Bluetooth mouse
- Bluetooth audio earbuds / headphones (Pixel Buds Pro 2)

Before the Fedora 44 upgrade, these devices reconnected automatically after being powered off and on again.

Since the upgrade, when the device is powered back on:
- it does not reconnect automatically;
- trying to connect manually from KDE Bluetooth settings fails after a few seconds;
- trying to connect manually with bluetoothctl also fails or hangs while printing unrelated BLE discovery events;
- the only reliable workarounds are:
  - remove / re-pair the device;
  - or reboot the computer;
  - in some cases restarting bluetooth.service may temporarily help.

This looks like a regression in the Bluetooth stack after upgrading to Fedora 44. It does not seem limited to a single device, since both a BLE mouse and Bluetooth audio devices are affected.

Version-Release number of selected component:

Fedora 44
KDE Plasma session

bluez: 5.86

Reproducible: Always

Steps to Reproduce:
Always or frequently after powering off a paired Bluetooth device and powering it back on.

1. Pair a Bluetooth device successfully.
   Tested with:
   - Logitech MX Anywhere 3S mouse
   - Bluetooth earbuds / headphones

2. Confirm that the device works normally while connected.

3. Power off the Bluetooth device.

4. Power it back on.

5. Wait for automatic reconnection.

6. If it does not reconnect, try to connect manually:
   - from KDE System Settings > Bluetooth;
   - or with:
     bluetoothctl connect <DEVICE_MAC>
Actual Results:
The device does not reconnect automatically.

Manual connection from KDE Bluetooth settings fails after a few seconds.

Manual connection with bluetoothctl does not successfully reconnect the device. In my case, bluetoothctl prints many unrelated BLE discovery events such as:

[CHG] Device xx:xx:xx:xx:xx:xx RSSI: ...
[CHG] Device xx:xx:xx:xx:xx:xx ManufacturerData...
[NEW] Device ...
[DEL] Device ...

but the target device does not reconnect.

For the mouse, the only reliable way to restore connectivity is to remove the device and pair it again, or reboot the system. The same kind of reconnection problem also occurs with Bluetooth audio devices.

Expected Results:
Previously paired and trusted Bluetooth devices should reconnect automatically after being powered off and on again.

Manual connection through KDE Bluetooth settings or bluetoothctl should reconnect the device without requiring re-pairing or a reboot.

Additional Information:
This started immediately after upgrading to Fedora 44.

The issue occurs with different kinds of Bluetooth devices, not only with the Logitech MX Anywhere 3S mouse.

A similar upstream BlueZ issue exists for Logitech MX Anywhere 3S reconnection problems:
https://github.com/bluez/bluez/issues/871

There are also Fedora / BlueZ reports around Bluetooth connection regressions and BlueZ 5.86, including bluetoothctl behavior in 5.86:
https://bugzilla.redhat.com/show_bug.cgi?id=2440346

Please let me know which additional logs would be useful. I can provide btmon output, bluetoothd logs, and device info output.