Oh, sweet! Somehow I failed to find that in my searching. Thanks!
On Mon, Jan 6, 2025 at 9:52 PM Kirill Primak wrote:
>
> Idea 2 has already been implemented
> (https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/368)
> and will be available in the next Wayland release.
>
>
>
(Note: to try to avoid overloading the word "client", I refer to the
wayland client as "the application" and explicitly say "the remote
desktop client" to refer to the machine the user is connecting from.)
They Wayland protocol currently delegates handling of keyboard
auto-repeat to the applicatio
Thanks all for the discussion so far.
The discussion of how things might work for gnome-remote-desktop
included calls to, e.g., org.gnome.Mutter.RemoteDesktop.CreateSession,
org.gnome.Mutter.RemoteDesktop.CreateOutput, and
org.gnome.Mutter.ScreenCast.CreateSession.
Ideally, Chrome Remote Desktop
On Thu, Apr 9, 2020 at 12:17 AM Jonas Ådahl wrote:
[snip]
> DRM master and input device revocation should be handled more or less
> already by most if not all compositors, by closing devices, by then
> going dorment until access is returned to the compositor. I don't know
> if there is any composi
On Wed, Apr 8, 2020 at 2:02 AM Jonas Ådahl wrote:
> Either multiple separate units (e.g. GDM and Chrome Remote Desktop login
> manager) needs to both try to manage the same sessions via logind, which
> sounds fragile and unlikely to be able to cope with the various security
> policies mentioned ab
