On Fri, 2024-03-01 at 19:03 +0100, René J.V. Bertin wrote: > On Friday March 01 2024 17:20:38 hw wrote: > > > Yeah, use rpd instead. Unfortunately, you can't seem to change the > > resolution when logging into a Gnome or a Wayland or X11 session from > > remote like you can with Windows. > > IIRC krdc has a connection dialog that allows you to chose a resolution. It's probably what I overlooked that one time I almost messed up my remote session. Yes, you can choose the resolution when logging in through xrdp. Once the resolution has been chosen, you can't change it. You also can't change the resolution when logging into another users session via rdp through Gnomes desktop sharing. When you log into a Windows session via rdp, you can change the resolution any time and not only before logging in, at least when logging in creates the session. I'm not sure if you can also change the resolution when taking over an existing session. > > Oh I mean only KDE and whatever else uses QT. > > With Qt it's a choice (assuming Qt6 still uses the same QPA > architecture; I've stayed away from it until now). So you can omit all X11 support with KDE/QT by compiling it without? That sure would be nice. > Gnome may have moved on to GTk4, but I have no idea if every application that isn't tied to that DE will have moved on from GTk2. And then there are DEs that last I checked were still using good old GTk2 with its extended theming support etc. As a widget library it really works just fine, after all. IIUC GTK works with wayland no matter what version (though emacs strangely doesn't). It would also be nice if everything GTK could be compiled without X11 support. That would be so much unused code that wouldn't have to be compiled in anymore. Once it's no longer needed, it won't need to be maintained anymore. > > That other platforms may keep Xorg alive doesn't mean that it would > > still work with Linux. > > Why wouldn't it, as long as Linux doesn't do anything to prevent it? Linux is not "the distros", after all. This is really no different than puritan distributions refusing to include any non-free software, and then installing applications like Google Chrome on them just because the developers give you a helping hand. Somehow I doubt that you could take, for example, Xorg and all the programs using it from some variant of BSD and compile it under Linux and have it magically work without any regard to or dependency on suitable graphics card drivers. > > Will the drivers > > continue to support Xorg on Linux and/or on other platforms when > > Wayland has replaced it? > > Linux is currently also being used in environments with serious needs for distributed computing, which probably also means being able to do remote advanced (3D) graphics. Think the automobile industry but also research environments. Lots of people providing the momentum to Xquartz alive work in the latter, for instance. > I would guess that XOrg and its drivers will remain on sufficient > life support to continue working as long as there is demand from end > users. In the end that's the big advantage of FOSS: everyone can > contribute and decide to keep it alive. It doesn't really matter what users demand, and that everyone can contribute is a myth. > Just look at the Trinity DE. What about it? > > What about adding new features to Xorg? > > Following the above, not impossible, but best not hold your breath. All that is assuming that Xwayland isn't already on par with XOrg, and won't ever be. If it is, the entire problem is moot already because X11 applications will just see a different server. It's not moot because Xorg and all related code could be omitted and nobody would need to bother with it. > > X11 forwarding is the worst option. > > It really is not, at least the version not using SSH isn't. It's an old protocol but really quite clever. It's not X11's fault that Qt5+ (and/or KDE5+ in particular) wasn't designed with optimal performance over remote X11 connections in mind. RDP and even VNC work much better. > > Krdc isn't too great, and how do you allow someone to join your KDE > > session from remote? > > Krdc is a remote desktop client (R D C). You need to run some server to enable remote connectivity to your desktop session. You could do that by hand (like I do), but also write a service definition that can be launched at login through the startup manager in KDE's systemsettings. That's probably what Gnome did, and that's also how Apple's remote desktop configuration works. Gnome requires a user to log in and to enable what they call desktop sharing before connections from remote are possible. With KDE, I wouldn't even know how to enable something like that at all. None of them can replace xrdp. So once there's no more Xorg, there's no xrdp, and connecting from remote like you can with xrdp is impossible. That's why I'm wondering what the replacement will be. And where is it?
Attachment:
signature.asc
Description: This is a digitally signed message part
