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.

      • just_another_person@lemmy.world
        2·
        16 days ago

        It certainly looks like this device is either: a) not maintaining a stable broadcast in low power mode, b) missing some standard BLE information that is expected to be broadcast, or c) your machine has duplicate UUIDs for this device.

        It’s hard to discern without being at the machine, so as a jumping off point, I would look at the devices your machine thinks it’s already paired with: bluetoothctl devices

        Copy and paste that list, and note the device IDs. Wait for this event to happen again, then check the bluetoothctl command again and see if the same mouse has registered with different IDs. If so, either the mouse is broadcast different device info all the time (weird), or you have a collision in the registered devices that isn’t being overwritten on pairing (also weird).

        SO…I’d say a good starting point after this is to just nuke all the registered BT devices:bluetoothctl remove {deviceID}

        See if that kicks things back into working. Have you tried new batteries by chance? Some of these BLE devices act super wonky if they don’t have perfect voltages. Sometimes Alkaline Batteries are needed instead of Lithium rechargeables even. Sounds dumb, but check the manuals to see if it’s mentioned.

        • glitching@lemmy.mlOP
          1·
          15 days ago

          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-2 on F43, bluez-5.83-2 on 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. tried diffing configs between them two but came up short.

          edit: same thing with this guy.

  • glitching@lemmy.mlOP
    1·
    15 days ago

    as described here adding the F42 repo, downgrading, and then blocking further updates fixes things immediately.