SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Suspend computer 2. Wake up computer OBSERVED RESULT Mouse not working (cursor not moving) EXPECTED RESULT Mouse working, cursor moving SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-53-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION HW restart of mouse (turn off/turn on) helps. This has started to happen after the latest Neon upgrade to Jammy.
dmesg: [156632.525056] Bluetooth: hci0: Waiting for firmware download to complete [156632.525715] Bluetooth: hci0: Firmware loaded in 1457966 usecs [156632.525761] Bluetooth: hci0: Waiting for device to boot [156632.540748] Bluetooth: hci0: Device booted in 14671 usecs [156632.540758] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc [156632.544759] Bluetooth: hci0: Applying Intel DDC parameters completed [156632.550737] Bluetooth: hci0: Firmware revision 0.3 build 126 week 5 2022 $ bluetoothctl Agent registered [400-MA102] Device B4:BC:7C:2F:CF:A5 (public) Name: 400-MA102 Alias: 400-MA102 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes WakeAllowed: yes LegacyPairing: no UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb) UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb) Modalias: bluetooth:v000Dp0000d0110 Battery Percentage: 0x32 (50)
So Bluetooth itself is still on after wake-from-sleep, but the device just doesn't automatically re-connect? Or it does automatically re-connect, but still doesn't work?
(In reply to Nate Graham from comment #2) > So Bluetooth itself is still on after wake-from-sleep, but the device just > doesn't automatically re-connect? Or it does automatically re-connect, but > still doesn't work? It seems to be connected, but it does not work. This has happened recently, but I can not pinpoint it to any change.
Thanks. In that case this is a regression below us; I'd recommend following up at https://github.com/bluez/bluez/issues.