Ferdinand Schober

Could you run `wayland-info` in that container and list the supported interfaces here? For input capture either the `wlr_layer_shell` protocol would need to be implemented or libei support is required...

gtk_shell1 _might_ be a valid fallback for layer_shell but at least [zwp_keyboard_shortcuts_inhibit_manager_v1](https://wayland.app/protocols/keyboard-shortcuts-inhibit-unstable-v1#zwp_keyboard_shortcuts_inhibit_manager_v1) would still be required to do anything useful. > If I can help debug integration any there let...

Cheers! You could do one more thing: Try to run with XDG_CURRENT_DESKTOP=KDE. That way we can tell whether or not the remote desktop portal is available. At least rudimentary input...

It must be capital KDE, what you want is the xdg-desktop-portal backend

Can you rerun this with LAN_MOUSE_LOG_LEVEL=debug?

Okay, seems like I need to add some more debug information first.

@jpeeler you can try the latest main now. I added a fallback interface so it does not crash before we know whats going on. XDG_CURRENT_DESKTOP=KDE is not required anymore

Okay seems like the remote desktop portal is not available. XTest likely wont work either.

> (Using [a6ab109](https://github.com/feschber/lan-mouse/commit/a6ab109faea8acd266fafe0a4c5a7e9b02c00fec)). > > ``` > $ LAN_MOUSE_LOG_LEVEL=debug ./lan-mouse > [2023-12-17T19:49:05Z ERROR lan_mouse::config] /home/jpeeler/.config/lan-mouse/config.toml: No such file or directory (os error 2) > [2023-12-17T19:49:05Z WARN lan_mouse::config] Continuing without config...

For input emulation only the remote desktop portal is required. (org.freedesktop.portal.RemoteDesktop). This has been around for a quite a while in xdg-desktop-portal-kde. Do I understand correctly that you are running...