[GH-ISSUE #152] KDE Plasma back to windows make mouse frozen #64

New issue

Closed

opened 2026-05-05 22:07:41 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 22:07:41 -06:00

Owner

Originally created by @Mzyhe3n6jmFqkYQyFKzFW3kGRGMok8xTYySN4Tm on GitHub (Jul 2, 2024).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/152

After #134 Windows can control Linux normally. But when back to Windows, the mouse and input will be frozen. There's only I can do is force a computer to shut down.

My linux system is fedora 40 KDE Plasma 6.1.1 Wayland, windows version is 26120.961.

Windows logs:

[2024-07-02T10:05:19Z INFO  lan_mouse::config] using config: "C:\Users\user\AppData\Local\lan-mouse\config.toml"
[2024-07-02T10:05:19Z INFO  lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt]
[2024-07-02T10:05:19Z INFO  lan_mouse::config] using config: "C:\Users\user\AppData\Local\lan-mouse\config.toml"
[2024-07-02T10:05:19Z INFO  lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt]
[2024-07-02T10:05:19Z INFO  lan_mouse] Press [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] to release the mouse
[2024-07-02T10:05:19Z INFO  lan_mouse::server] running service
[2024-07-02T10:05:19Z INFO  lan_mouse::capture] using capture backend: windows
[2024-07-02T10:05:19Z INFO  lan_mouse::emulate] using emulation backend: windows
[2024-07-02T10:05:19Z INFO  lan_mouse::dns] resolving 192.168.8.37 ...
[2024-07-02T10:05:19Z INFO  lan_mouse::dns] 192.168.8.37: adding ip 192.168.8.37
[2024-07-02T10:05:20Z INFO  lan_mouse::capture::windows] [92, 92, 46, 92, 68, 73, 83, 80, 76, 65, 89, 49, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

Linux logs:

[2024-07-02T10:06:41Z INFO  lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt]
[2024-07-02T10:06:41Z INFO  lan_mouse] Press [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] to release the mouse
[2024-07-02T10:06:41Z INFO  lan_mouse::server] running service
[2024-07-02T10:06:41Z WARN  lan_mouse::emulate] could not create input emulation backend: wlroots backend: wlr-virtual-pointer-unstable-v1 protocol not supported: the requested global was not found in the registry
[2024-07-02T10:06:41Z INFO  lan_mouse::dns] resolving 192.168.8.159 ...
[2024-07-02T10:06:41Z INFO  lan_mouse::dns] 192.168.8.159: adding ip 192.168.8.159
[2024-07-02T10:06:41Z INFO  lan_mouse::emulate::libei] requesting permission for input emulation
[2024-07-02T10:06:43Z INFO  lan_mouse::emulate] using emulation backend: libei
[2024-07-02T10:06:43Z INFO  lan_mouse::emulate::libei] libei version 1
[2024-07-02T10:06:44Z INFO  lan_mouse::capture] using capture backend: input-capture-portal

Originally created by @Mzyhe3n6jmFqkYQyFKzFW3kGRGMok8xTYySN4Tm on GitHub (Jul 2, 2024). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/152 After #134 Windows can control Linux normally. But when back to Windows, the mouse and input will be frozen. There's only I can do is force a computer to shut down. My linux system is fedora 40 KDE Plasma 6.1.1 Wayland, windows version is 26120.961. Windows logs: ``` [2024-07-02T10:05:19Z INFO lan_mouse::config] using config: "C:\Users\user\AppData\Local\lan-mouse\config.toml" [2024-07-02T10:05:19Z INFO lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] [2024-07-02T10:05:19Z INFO lan_mouse::config] using config: "C:\Users\user\AppData\Local\lan-mouse\config.toml" [2024-07-02T10:05:19Z INFO lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] [2024-07-02T10:05:19Z INFO lan_mouse] Press [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] to release the mouse [2024-07-02T10:05:19Z INFO lan_mouse::server] running service [2024-07-02T10:05:19Z INFO lan_mouse::capture] using capture backend: windows [2024-07-02T10:05:19Z INFO lan_mouse::emulate] using emulation backend: windows [2024-07-02T10:05:19Z INFO lan_mouse::dns] resolving 192.168.8.37 ... [2024-07-02T10:05:19Z INFO lan_mouse::dns] 192.168.8.37: adding ip 192.168.8.37 [2024-07-02T10:05:20Z INFO lan_mouse::capture::windows] [92, 92, 46, 92, 68, 73, 83, 80, 76, 65, 89, 49, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] ``` Linux logs: ``` [2024-07-02T10:06:41Z INFO lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] [2024-07-02T10:06:41Z INFO lan_mouse] Press [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] to release the mouse [2024-07-02T10:06:41Z INFO lan_mouse::server] running service [2024-07-02T10:06:41Z WARN lan_mouse::emulate] could not create input emulation backend: wlroots backend: wlr-virtual-pointer-unstable-v1 protocol not supported: the requested global was not found in the registry [2024-07-02T10:06:41Z INFO lan_mouse::dns] resolving 192.168.8.159 ... [2024-07-02T10:06:41Z INFO lan_mouse::dns] 192.168.8.159: adding ip 192.168.8.159 [2024-07-02T10:06:41Z INFO lan_mouse::emulate::libei] requesting permission for input emulation [2024-07-02T10:06:43Z INFO lan_mouse::emulate] using emulation backend: libei [2024-07-02T10:06:43Z INFO lan_mouse::emulate::libei] libei version 1 [2024-07-02T10:06:44Z INFO lan_mouse::capture] using capture backend: input-capture-portal ```

gitea-mirror closed this issue

2026-05-05 22:07:42 -06:00

gitea-mirror commented

2026-05-05 22:07:44 -06:00

Author

Owner

@feschber commented on GitHub (Jul 2, 2024):

You mean the mouse is frozen in windows or in KDE?
In case you mean KDE: See #140, you need to add

capture_backend = "LayerShell"

on the top of your lan-mouse config until that issue is resolved.

@feschber commented on GitHub (Jul 2, 2024): You mean the mouse is frozen in windows or in KDE? In case you mean KDE: See #140, you need to add ```toml capture_backend = "LayerShell" ``` on the top of your lan-mouse config until that issue is resolved.

gitea-mirror commented

2026-05-05 22:07:45 -06:00

Author

Owner

@Mzyhe3n6jmFqkYQyFKzFW3kGRGMok8xTYySN4Tm commented on GitHub (Jul 2, 2024):

Thank you. Is working right now.

@Mzyhe3n6jmFqkYQyFKzFW3kGRGMok8xTYySN4Tm commented on GitHub (Jul 2, 2024): Thank you. Is working right now.