Thanks for following up on my report. I was already unable to use Ubuntu 24 due to the inability to use VNC servers with x.org . I’m obviously not going to jump on a non LTS version that drops it. I really hope someone will be working on this for the next LTS in 2026. Otherwise, I will be looking to another distro. It is really hard to believe that only 2 people are affected by this.
I will not use any tool that requires cloud access to access my LAN devices. My ISP goes down at times, but my router still operates. So I think that means tools like Teamviewer are out.
Command Prompts Menus are the way Document Editor is doing things via API. In the Xorg days it could sends Instructions via Network and Render OpenGL/(EGL?) as remote application locally via some xorg protocol extensions madness.
sending Streams of GPU instructions is hard, but Reactive (Streams) in HTML(and Game) world is a Reality and today also in Video Server Hosting if Data Traffic Packages allows which is weird even for Apps hostings traffic Downloads.
but Sending Instructions What to Do is framework agnostic, so even Sending Instructions as Command Prompt via API is possible to tell remote API to do something. And today it is possible to tell remote browser to do something. VIA classic browser headless API or even Chrome native Protocol to implement Command Prompt API or some chosen framework or implementation if found or programmed.
So the old way to tell remote to send GPU instructions is maybe on Wayland Protocol still needed(translation Mesa protocol? implementation if allowed like is Mesa full of them, but when IEEE, ECMA(international), IETF standards developed(even some IANA) it could industry help as even Message Posting Protocols is communications awareness ahead),
but Reactive Streams are Today HTML/… reality but as always other tech details are still hard for developers to make their jobs and solve their CV, maybe some xorg foundation grants ahead but that is consortium industry thing behind curtain.
Zoom supports Wayland (I use it regularly!), it will automatically use portals on GNOME, and it needs to be lied to for other Wayland environments (XDG_CURRENT_DESKTOP=GNOME is required to allow portal functionality).
RustDesk supports Wayland and is aimed as an open source alternative to AnyDesk specifically.
It seems to be a normal app, I expect it to work fine on Wayland. Qt5 supports Wayland, as does LibreOffice. VLC should be okay too.
Yes, we have recently split the plasma sessions out into 2 separate packages, plasma-session-wayland and plasma-session-x11. At the moment we intend to ship the wayland one by default on the ISO and installs, while users who still want an X11 session will be free to install the X11 one.
As of a few days ago Ubuntu Desktop 25.10 is Wayland only. The log-in screen itself will now always run in Wayland mode[1], and it only allows logging-in to Wayland desktops.
The second part of that statement is expected to change before the Ubuntu 25.10 release as the GNOME Team is working on restoring the ability to log-in to X11 desktops, for those people using the GNOME log-in screen (GDM) to log-in to non-GNOME desktops.
Currently the Ubuntu on Xorg session still exists but is not accessible from the GNOME log-in screen (GDM); this will be removed next.
_
[1]: It already did in the vast majority of cases, except in virtual machines with GPU pass-through, or when falling-back to Xorg from a failed attempt to show the log-in screen in Wayland mode.
One problem I have with Wayland is its inability to use two monitors when opening a remote session with Remmina. As @pnowack already pointed out, this is a known issue. This means I can’t use Wayland, not because I’m choosy or dislike it, but because it lacks fundamental functionalities essential for my work.
I’m guessing multi-monitor remote desktop looked like a single monitor at the client end? This would have worked with Xorg at the server end because Xorg has the limitation (not a feature) that it updates all monitors from a single framebuffer. This is really a bug in Xorg for local users because it causes tearing and incorrect frame rates on at least half the monitors. So it’s not something Wayland sessions are ever going to copy. If remote multi-monitor support is desired then that will need to be implemented explicitly at the server end.
Yes there are at least two exceptions to the rule that won’t tear:
Some Xorg drivers will delay scanout (triple buffer) on all but one monitor in their XRandr implementation.
Xinerama I think can physically separate the X displays and only make them logically adjacent.
But tearing isn’t really the issue. The main issue is in the common case of XRandr that all monitors share a single framebuffer and Wayland compositors are unlikely to do that for performance reasons.
If however a Wayland compositor supported true headless remote desktops with no real monitors at the server end, then it would be straightforward. But it’s up to the compositor to implement that.
via XRandr you could also instill on Monitor mode, colors and its spaces and similars like resolutions and also even own modesets resolutions if there is some incompatibility or some freqs tweaks neccessary(probably for non-standard monitor vendors). But its limitations to monitors is only partly what hw is capable for other parts of PC space outside of pc nerds in various professions. And reality is that vendors are part of that space even when not on linux channels… weird said for XRandr capabilities of unknown domains often presents on some CGA old monitors setup from 80s with distilled colors and text or some maybe today health monitor stacks.
Video-conferencing actually works under Wayland (zoom, kmeet based on jitsi)
But OpenLP is definitely not usable at present (version 3.1). I hope version 4 will work with Wayland and be ready before the next Ubuntu LTS…
Anydesk does not work and Teamviewer is not a replacement for me (I did use Teamviewer at first, it worked well for some time, then I started to be rejected frequently although I am helping friends and coworkers in an NGO, NOT working in any commercial setting, so I had to swith to Anydesk)
Wayback is for running X11 only desktop environments but using rootful Xwayland instead of the regular Xorg binary. The idea being that Xwayland is better maintained than Xorg since Xwayland still has importance in a Wayland world.
It has no relevance in this case. Gnome is going Wayland only, so there is no X11 Gnome session to run using Wayback. Gnome will run as a native Wayland session and use Xwayland to run X11 windows.
Thanks for that information. I can make a patch to make sure OpenLP works from the launcher instead of from the terminal. That should keep it working for at least this cycle until the OpenLP people decide to convert to Wayland.
I’m still concerned about the drop of X11. I’m relying on the screen sharing functionality of Microsoft Teams, Slack and Discord. I’ve tested Gnome on Wayland with Ubuntu 25.10 as well as with the latest Fedora. If I share my screen when using Xwayland, the video stream goes down to like 5 FPS. When sharing my screen on wayland natively, the FPS and quality is good, but the viewer will see weird artifacts in the video stream almost permanently.
Another problem I have is running games with Wine/Proton. By default it seems they are using Xwayland, which let the FPS drop to 15-20. When forcing proton to use wayland, the fps will be fine, but there are many small bugs that make the whole gaming experience annoying (glitching graphics, not disappearing cursor even when it should etc.
To be honest, I’ll probably just stay on Ubuntu 24.04 with Gnome on Xorg for some more years until the ecosystem is really ready for wayland.
