mirror of
https://github.com/feschber/lan-mouse.git
synced 2026-05-15 06:06:07 -06:00
[GH-ISSUE #245] Wayland(sway) to Windows error #120
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#120
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 @NeveIsa on GitHub (Dec 22, 2024).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/245
On windows I get this error on the terminal whenever my cursor of sway hits the border.
The windows device is LenovoSlim7x running Windows11 on Snapdragon XElite ARM Processor.
WARN lan_mouse::server::emulation_task] network error: network error:
A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself. (os error 10040)@feschber commented on GitHub (Dec 22, 2024):
could you confirm that you are running the same version on both devices?
@NeveIsa commented on GitHub (Dec 24, 2024):
Yes, they are both the latest.
@Horghski commented on GitHub (Jan 12, 2025):
I'm getting the same error, trying to connect from Hyprland on Arch Linux to a Windows 11 laptop. I actually just opened https://github.com/feschber/lan-mouse/issues/248 to track that, but it may be the same issue?
@Horghski commented on GitHub (Jan 12, 2025):
@NeveIsa are you by any chance running Arch, btw? I ask since I just figured out that Arch still has lan-mouse 0.9.1 in the official repo, while I was using 0.10 on my Windows laptop. I just downgraded to 0.9.1 on Windows and now things are working.
@Vassili-Dev commented on GitHub (Jul 2, 2025):
I've had this issue when using the v0.10.0 Windows binary (I suspect the actual build is not v0.10.0 but idk why). If you're downloading the pre-built windows binary, try the development build.
@nfriday commented on GitHub (Aug 13, 2025):
I can second this, the v0.10.0 Windows binary yields the error in the original post whereas the development build works.
@feschber commented on GitHub (Feb 7, 2026):
Feel free to reopen, if you can not get it to work!