so I have this Rapoo BLE/BT3.0 mouse for years and it worked without issues up until Fedora 42. initially it worked there as well but after a bluez update it started with this shit.
everytime it goes to sleep due to inacitivity and then tries to reconnect on movememt or button press, it prompts me to authorize it. I’ve of course clicked trust and authorize with another mouse but it won’t get remembered.
I’ve tried using bluetoothctl to manually pair, authorize, and connect and it don’t make no difference. it behaves thusly on every BT controller I’ve tried, intel, broadcom, USB and onboard.
the mouse has two modes, BLE and BT3.0 and this behaviour is only with BLE, which is far superior - way faster tracking, reaction, reconnect, etc. - and I really don’t wanna use the BT3.0 option.
on F42 there was a solution - downgrade bluez to the stack shipped with the initial install and exclude it from dnf upgrades. it starts working immediately after downgrade with zero issues. on F43 there is no such option.
tried searching but apart from some poor soul with the same mouse, no sensible clues.
any ideas on what to look up as I know dick about the whole bluetooth stack. please no chantgpt suggestions, thanks.
appreciate the attempt, went through some of those, but I think you’re on the wrong track. this issue persists across different machines and installs - F42, F43, old installs and fresh ones, desktop, laptop… the only common denominators are this crappy mouse and current bluez version (
bluez-5.84-2on F43,bluez-5.83-2on F42). the moment it’s back atbluez-5.80-1(available only on F42) everything works, no need to reboot, no prompts to reconnect, nada. trieddiffing configs between them two but came up short.edit: same thing with this guy.