github-starred/lan-mouse

Fork 0

mirror of https://github.com/feschber/lan-mouse.git synced 2026-05-15 22:01:59 -06:00

[GH-ISSUE #193] Recover from `Resource temporarily unavailable` error #85

New issue

Open

opened 2026-05-05 22:08:34 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 22:08:34 -06:00

Owner

Originally created by @xf- on GitHub (Sep 6, 2024).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/193

If network is busy or the system is under high load it will throw a warning and a restart of lan-mouse is required.

Error

WARN  lan_mouse::server::emulation_task] input emulation exited: error emulating input: `io error: `Resource temporarily unavailable (os error 11)``

Would be nice to restart the handshake or whatever is at fault so it can recover from such an error.

Originally created by @xf- on GitHub (Sep 6, 2024). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/193 If network is busy or the system is under high load it will throw a warning and a restart of lan-mouse is required. **Error** ``` WARN lan_mouse::server::emulation_task] input emulation exited: error emulating input: `io error: `Resource temporarily unavailable (os error 11)`` ``` Would be nice to restart the handshake or whatever is at fault so it can recover from such an error.

gitea-mirror commented

2026-05-05 22:08:38 -06:00

Author

Owner

@feschber commented on GitHub (Sep 7, 2024):

this should prompt you to reenable input emulation like this:

is that correct?

It would make sense to try recovering immediately without a prompt in some cases, but I wanted to avoid a situation where it constantly tries to reactivate the input emulation and fails (e.g. when the wayland compositor is terminated).

Will see what I can do.

@feschber commented on GitHub (Sep 7, 2024): this should prompt you to reenable input emulation like this: ![image](https://github.com/user-attachments/assets/edef3466-0fe7-4e42-b4f1-8616ef0126ee) is that correct? It would make sense to try recovering immediately without a prompt in some cases, but I wanted to avoid a situation where it constantly tries to reactivate the input emulation and fails (e.g. when the wayland compositor is terminated). Will see what I can do.

gitea-mirror commented

2026-05-05 22:08:38 -06:00

Author

Owner

@xf- commented on GitHub (Sep 7, 2024):

I have no libadwaita and run it on cli. Maybe add an option for it. Feels like no retry or do 1 sec 10 sec 30 sec and afterward stop.

cargo build --release --no-default-features --features wayland,xdg_desktop_portal,libei

@xf- commented on GitHub (Sep 7, 2024): I have no `libadwaita` and run it on cli. Maybe add an option for it. Feels like no retry or do 1 sec 10 sec 30 sec and afterward stop. ``` cargo build --release --no-default-features --features wayland,xdg_desktop_portal,libei ```

gitea-mirror commented

2026-05-05 22:08:39 -06:00

Author

Owner

@feschber commented on GitHub (Sep 7, 2024):

Ah okay that makes sense, I have not implemented any way of reenabling the emulation via cli (yet).

Some sort of timeout would probably make sense for recoverable errors, yeah

@feschber commented on GitHub (Sep 7, 2024): Ah okay that makes sense, I have not implemented any way of reenabling the emulation via cli (yet). Some sort of timeout would probably make sense for recoverable errors, yeah

gitea-mirror commented

2026-05-05 22:08:40 -06:00

Author

Owner

@feschber commented on GitHub (Sep 10, 2024):

by the way: How often does this happen? And it would be good to know what backends are being used.

@feschber commented on GitHub (Sep 10, 2024): by the way: How often does this happen? And it would be good to know what backends are being used.

gitea-mirror commented

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

Author

Owner

@xf- commented on GitHub (Sep 10, 2024):

by the way: How often does this happen? And it would be good to know what backends are being used.

Depends a lot on circumstances. Most common under high load (system or network). I sometimes feel like the switch is at its limit with 2.5 Gbit.

wayland - wayland

High load: Few seconds or every minute
No load: Never an issue/weeks/months

@xf- commented on GitHub (Sep 10, 2024): > by the way: How often does this happen? And it would be good to know what backends are being used. Depends a lot on circumstances. Most common under high load (system or network). I sometimes feel like the switch is at its limit with 2.5 Gbit. wayland - wayland High load: Few seconds or every minute No load: Never an issue/weeks/months