https://bugs.kde.org/show_bug.cgi?id=520062
--- Comment #3 from [email protected] --- (In reply to David Edmundson from comment #1) > >I got the back/forward buttons working with the following patch locally: > > I'm surprised we're not mapping to BTN_BACK/BTN_FORWARD. I tested the MR locally https://invent.kde.org/plasma/krdp/-/merge_requests/171 but the back/forward mouse buttons do not work. I believe it needs to be BTN_SIDE and BTN_EXTRA. AI gave me the following explanation: The logs point to a likely **mapping mistake**, not a transport problem. ### What the logs prove KRDP: - receives Remmina’s extended mouse events - routes them through the portal backend So the remaining likely bug is the **evdev code** we send. ### Likely issue We currently map: - `Qt::BackButton -> BTN_BACK (278)` - `Qt::ForwardButton -> BTN_FORWARD (277)` But RDP’s extended buttons are really **XBUTTON1/XBUTTON2**, and Qt shows that too: - `BackButton == XButton1 == ExtraButton1` - `ForwardButton == XButton2 == ExtraButton2` On Linux, the more likely evdev mapping for those is: - `Qt::BackButton -> BTN_SIDE (0x113 / 275)` - `Qt::ForwardButton -> BTN_EXTRA (0x114 / 276)` `BTN_BACK/BTN_FORWARD` are usually later extra mouse buttons, not the standard X1/X2 pair. -- You are receiving this mail because: You are watching all bug changes.
