mirror of
https://github.com/feschber/lan-mouse.git
synced 2026-05-15 06:06:07 -06:00
[GH-ISSUE #357] [Linux client + MacOS server] Sticky modifier keys #186
Labels
No labels
Xorg
documentation
enhancement
macos
pull-request
question
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/lan-mouse#186
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kiwiz on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/357
Client (IO source): KDE/Wayland, Ubuntu, commit:
3922b45bd9Server: MacOS, commit:
640fa995a4When performing key combinations (ex: meta+tab), the modifier key appears to get stuck down. Hitting the key again resets the state. FWIW, MacOS -> MacOS works perfectly fine.
@kiwiz commented on GitHub (Jan 12, 2026):
Mac -> Mac
Linux -> Mac
It looks like
modifier_eventisn't being called in certain cases.@feschber commented on GitHub (Feb 6, 2026):
which input-capture backend is used on linux?
@kiwiz commented on GitHub (Feb 7, 2026):
Wayland (KDE)
@kiwiz commented on GitHub (Feb 7, 2026):
Ah sorry, it's libei
@kenichi commented on GitHub (Feb 11, 2026):
Thanks for a great tool! I've been having this exact problem, except Gnome/Wayland, still libei. So far, this branch is working for me:
https://github.com/kenichi/lan-mouse/tree/linux_to_macos_fix
can test with
cargo install --git https://github.com/kenichi/lan-mouse.git --branch linux_to_macos_fix@feschber commented on GitHub (Feb 11, 2026):
@kenichi are you open to making a PR?
@kenichi commented on GitHub (Feb 11, 2026):
@feschber yes, no problem. though I'm not sure about affects to other OS combos 🤷🏽♂️
@feschber commented on GitHub (Feb 13, 2026):
We might get duplicated modifier events but I don't think that should cause any problems.
Eventually I think its best to handle modifier events entirely client side but as a temporary fix this is certainly okay!