Bug 485045

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Whenever the bluetoothd service is left to idle for a period of time (30min to an hour or more), it becomes unresponsive. When attempting to manually restart the service, the terminal hangs when attempting to run the cmd with systemctl. Interestingly, I noticed that the bluetoothd service is consuming a lot of cpu whenever it becomes unresponsive.
In other cases when the bluetooth is left to idle after remaining connected to a device, the device still is able to play audio but the bluetooth widget doesn't correctly display the status under the connected device. More specifically, the button under the device displays 'connect' even though the device is already connected. The battery information is also displayed under the connected device but the button is displayed as connect which makes it impossible to disconnect the device through the widget or connect to some other device.


STEPS TO REPRODUCE
1. Enable bluetooth and connect to some device.
2. Leave the bluetooth device and host machine to idle for 30min to an hour.
3. Interact with the bluetooth widget in order to see whether it is behaving properly or not.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 
Qt Version: 6

ADDITIONAL INFORMATION