Wayland, perhaps that wasn't a great plan...
Wayland, perhaps that wasn't a great plan...
GNOME and KDE both offer RDP via Wayland, with GNOME’s version fully functioning in a headless setup. If your goal is simply to transmit data using SSH, Pipewire remains functional even when xwayland is active. RHEL has removed xorg-server entirely. Regarding hardware compatibility, support tends to diminish over time due to kernel changes, outdated modules, project neglect, or lack of mainstream software backing it. RHEL has fully transitioned to x86_64-v3, while Fedora, OpenSUSE, and Ubuntu are all gearing up for a gradual shift. This transition often disrupts existing setups. Screen capture issues have been resolved thanks to XDG Desktop Portal and Pipewire. Legacy applications persist because they rely on older software that may not align with newer compositors. NVIDIA has generally kept pace with Wayland adoption, though it still varies by developer. The main challenge remains that most major BSD distributions lag in comprehensive Wayland support, a pattern common for BSD systems.
GNOME provides a fully headless setup with software rendering for RDP sessions. See the relevant documentation links for details on remote desktop configuration and administration.
Few still rely on that method compared to remote desktop options. Most users won’t notice the change, but they might feel the impact of improvements like enhanced VRR in Wayland. The concern arises because outdated software becomes impractical. If your system uses old hardware incompatible with Wayland, sticking to X11 remains an option. Because it’s free software, anyone can keep supporting it as required. This encourages development of newer solutions for current devices.
Minimal but sufficient for the project's survival. I think the X will receive only very sparse assistance, with updates coming in a somewhat inconsistent manner—similar to how sysvinit functioned before systemd.
Using SSH becomes simpler when connecting via the internet and you need a secure connection with little effort. You just need to open a port and set up public key authentication, giving you safe access to your remote files and desktop. There are many other options to reach the same goal. People aren’t insisting it must stop working, even though there’s a lot of discussion around KDE phasing it out for their desktops and apps still backing it. There are still many window managers and desktop environments that support it, and probably will for the near future. Still, if Wayland is meant to become the standard, it should naturally replace X11 by default so most users switch without needing to stick with X11.
You're free to route any traffic through SSH, which makes the value of X11 less clear compared to other options, aside from possibly saving bandwidth. In my view, most remote tasks requiring a desktop environment are still Windows-based today. It might have made sense when it was first created, but I don't see much necessity now. KDE isn't the only choice—Gnome 49 turns it off by default and Gnome 50 removes support entirely. Still, I mostly stick with X11 myself; Wayland makes drag-and-drop problematic on my Wacom for gaming, where VRR performance is important.
It's mainly about how simple it is to set up and operate. I'm sure the main issue was KDE's recent announcement. Regardless, if you require X11 support, there are still options available to maintain usage for a long time.
X11 isn't functioning properly on my setup, so I switched from LMDE to Fedora 43. The refresh rate is off, and the display goes blank intermittently every few hours. Wayland should be better.