KDE prompts Remote Control Request muliple times and answer doesn't matter.

[CupricReki]

I'm getting multiple Remote Control Request every time I launch lan-mouse from the CLI.

Log

❯ lan-mouse
[2024-01-15T14:52:24Z INFO  lan_mouse::config] using config: "/home/cupric/.config/lan-mouse/config.toml"

(lan-mouse:1668930): Gtk-WARNING **: 09:52:24.175: Unknown key gtk-modules in /home/cupric/.config/gtk-4.0/settings.ini
[2024-01-15T14:52:24Z INFO  lan_mouse::config] using config: "/home/cupric/.config/lan-mouse/config.toml"
[2024-01-15T14:52:24Z INFO  lan_mouse] Press Ctrl+Alt+Shift+Super to release the mouse
[2024-01-15T14:52:24Z INFO  lan_mouse::consumer] wayland backend not available: the requested global was not found in the registry
[2024-01-15T14:52:24Z INFO  lan_mouse::producer] libei event producer not available: not implemented
[2024-01-15T14:52:24Z INFO  lan_mouse::producer] using layer-shell event producer

(lan-mouse:1668930): Adwaita-WARNING **: 09:52:24.261: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

[2024-01-15T14:52:34Z INFO  lan_mouse::consumer] libei not available: Portal request failed: org.freedesktop.zbus.Error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'ConnectToEIS' in interface 'org.freedesktop.impl.portal.RemoteDesktop' at object path '/org/freedesktop/portal/desktop' (signature 'osa{sv}')

Remote Control Request prompt shows a second time.

[2024-01-15T14:52:40Z INFO  lan_mouse::consumer] using xdg-remote-desktop-portal event consumer
[2024-01-15T14:52:49Z INFO  lan_mouse] terminating service
[2024-01-15T14:52:49Z INFO  lan_mouse::server] terminating service
[2024-01-15T14:52:49Z INFO  lan_mouse::server] terminating gracefully...

Notes

• Interestingly, it doesn't matter how if I accept or not, lan-mouse still works.
• When launching via lan-mouse I don't always get the prompt, but I do get a notification.
  

[feschber]

The reason it shows up twice is that it first tries to connect to Libei, which is done through the same RemoteDesktopPortal interface as the actual remote desktop portal backend.

KDE does not implement Libei yet so that fails. Then the remote desktop portal requests access again.

It would be possible to work around this by simply requesting the remote desktop portal on KDE directly instead of Libei (I actually did this in earlier versions until I changed it to this fallback based system) but I'd rather leave it like this until KDE supports libei (I dont know how long that is going to take maybe I can look into it if I have the time).

As far as I have seen, KDE does not ask again once the permission has been granted once for a specific application so I dont think this should be a large issue but let me know your thoughts.

[CupricReki]

I'm not sure what triggers the permission prompt to be again after being accepted the first time. Perhaps the issue will go away now that that I'm installing/updating via the AUR.

Keeping this open for now.

[CupricReki]

Bummer about Libei. But it looks like it might come to Plasma 6.1 https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/issues/12.

[feschber]

I'm not sure what triggers the permission prompt to be again after being accepted the first time. Perhaps the issue will go away now that that I'm installing/updating via the AUR.

Keeping this open for now.

Did you test this? I am not getting prompts after accepting it for the first time.

[feschber]

something must have changed because I see the prompt everytime now as well. Will see what I can do about that

[CupricReki]

Did you update to Plasma 6?

…

On Sat, Mar 16, 2024, 7:59 PM Ferdinand Schober ***@***.***> wrote: something must have changed because I see the prompt everytime now as well. Will see what I can do about that — Reply to this email directly, view it on GitHub <#74 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRVFEDRXOK2U5GNYKKUYJDYYSI7XAVCNFSM6AAAAABB3ODEYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGA4DSMBRGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[feschber]

Yes but I can not say 100% if that was the point where it started. Will need to check

[svillar]

I've seen the same in GNOME FWIW

[feschber]

What version of GNOME are you using? Starting at 45, it should only ask once as libei is now supported.

I also changed the behaviour in 0.7 now, such that it asks again if the request is cancelled. So technically it now works as intended.

I could maybe look into merging the backends into one or reuse the same portal but idk if thats actually possible even.

[svillar]

What version of GNOME are you using? Starting at 45, it should only ask once as libei is now supported.

Ah maybe that's the reason, I've 45-46 in one machine but 43 in another one. Actually I couldn't make the software work at all, clients are detected but cannot share the keyboard/mouse among them. I've tried both Wayland and X11 sessions (actually the reason to try lan-mouse is the wayland support, because for X11 Ilaready have barrier working fine) I've installed libei in all the computers but shows still as unsupported

[feschber]

Yeah libei alone won't help because gnome does not implement the input capture portal until version 45.

[svillar]

Yeah libei alone won't help because gnome does not implement the input capture portal until version 45.

And should it work using any other fallback? I'm just trying to know whether this mix of GNOME 45 with 43 should work and then the problem is my configuration, or instead, I should wait till GNOME 45 in stable

[feschber]

And should it work using any other fallback?

Unfortunately not, no. Gnome does not support the layer-shell protocol.

[CupricReki]

Since updating to Plasma 6 I see two prompts every time we I start lan mouse