https://bugs.kde.org/show_bug.cgi?id=481912
--- Comment #27 from Robin Bankhead <[email protected]> --- (In reply to Klaus Kusche from comment #26) > Can someone already tell if this is going to be a desktop-independent > remoting solution > or a KDE-specific solution? > > I was told that a desktop-independent solution is technically impossible in > Wayland, > because any remoting solution needs additional code in the compositor, > and hence there can be no remoting solution which works with any compositor > or desktop environment. > > Hence, it would be impossible to have a terminal server with wayland > where the users are free to choose their desktop environment or compositor. > X11 can easily support this, so this would be a showstopper for wayland. The most that has been disclosed on the subject (that I've seen) was recently by David Edmundson here: https://discuss.kde.org/t/plasma-6-8-and-plasma-login-manager/48643/28 A desktop-agnostic approach is discussed there among other things, but it's anyone's guess when or whether this will take shape. Different compositors are all at different places with this: Gnome already has full headless remoting; wlroots has it via wayvnc; Weston also has it with VNC and RDP backends, though I've found them hit-and-miss. Whether there is collective will to unify on this, I can't say. A virtual/dummy display backend does seem to be one thing each compositor needs to organise for itself; all the above do, so does kwin, but while running a full session solely on it has been accomplished in dev according to David's comment above, the wherewithal for trying this out is not out in the wild for anyone to test yet. And the actual login side of things is still a whole other ball of wax, probably a great deal more fiddly actually. For how things are going over at an existing DE-agnostic RDP project looking into how to support Wayland, you may want to have a look at this: https://github.com/neutrinolabs/xrdp/issues/2637 My last thought as to how to stay informed about any of KDE's work on this starting to hit the repos is to keep tabs on the activity logs of devs involved in that work. -- You are receiving this mail because: You are watching all bug changes.
