https://bugs.kde.org/show_bug.cgi?id=435338
--- Comment #10 from Bogdan Bivolaru <bogdan.bivol...@gmail.com> --- (In reply to Bogdan Bivolaru from comment #9) > (In reply to Josh from comment #8) > > Issue is only when connecting to a wayland session, not from. Sorely > > affected by this as well and have been for some time. Is there a wl-roots > > standard that would assist us in resolving this problem? > > I _guess_ this is relevant here: > Wayvnc is a VNC server for WL-roots based compositor > https://github.com/any1/wayvnc/tree/master/protocols: > at minimum I guess we would need virtual-keyboard-unstable-v1.xml and > wlr-virtual-pointer-unstable-v1.xml > > Gnome VNC source code confuses me a lot, I do not understand if this feature > is implemented or not: > https://gitlab.gnome.org/ > search?search=keyboard&group_id=&project_id=12409&scope=&search_code=true&sni > ppets=false&repository_ref=master&nav_source=navbar > > I would have hoped that all the remote desktop streams would be handled via > pipewire eventually. My logic is that all stream types need buffering and to > be routed from a producer node to a consumer. Since some are more latency > dependent than others it would be great if there was a panel where mixing > and matching streams could be made... say like WirePlumber session manager. > I don't see why video, audio streams need to be managed separately from > keyboard, mouse, clipboard, other data event streams. UPDATE: comment from the Elsie Hupp, author of (any1)[https://github.com/any1/wayvnc/discussions/93#discussioncomment-741946] I wouldn't be opposed to a PR implementing Gnome support, but I'd much rather that the Gnome people implement proper wayland protocols for screen capturing instead of putting everything on dbus -- You are receiving this mail because: You are watching all bug changes.
