


KDE had to do additional work to work around it. no global menu on Wayland, I thought, not without significant re-engineering effort"). ("it uses global window IDs, which don’t exist in a Wayland world. Wayland broke global menus with KDE platformplugin ❌ broken since ("because the lack of the Gtk+ Wayland support for the Global Menu").Wayland breaks Gnome-Global-AppMenu (global menus for Gnome) This is an X11 application, and as such will not function 100% onĭistributions that default to using Wayland instead of Xorg. Wayland breaks automation software sudo pkg install p圓7-autokey probonopd/Zoom.AppImage#8 ❌ broken since Zoom: "You need PulseAudio 1.0 and above to support audio share" on a system that uses pipewire-pulseaudio.("Can not start share, we only support wayland on GNOME with Ubuntu (17, 18), Fedora (25 to 29), Debian 9, openSUSE Leap 15, Arch Linux"). flathub/us.zoom.Zoom#22 Zoom ❌ broken since at least.jitsi/jitsi-meet#6389 ❌ broken since ("Closing since there is nothing we can do from the Jitsi Meet side.") See? Wayland breaks stuff and leaves application developers helpless and unable to fix the breakage, even if they wanted.Wayland breaks screen sharing applications There is a workaround for OBS Studio that requires a obs-xdg-portal plugin (which is known to be Red Hat/Flatpak-centric, GNOME-centric, "perhaps" works with other desktops).("Wayland is unsupported at this time", "There isn't really something that can just be easily changed. obsproject/obs-studio#2471 ❌ broken since at least.Wayland breaks everything and then expects others to fix the wreckage it caused on their own expense. Let's see how it looks in a year or two.") - This is the key problem. ("I have now decided that there will be no Wayland support for the time being. vkohaupt/vokoscreenNG#51 ❌ broken since at least.❌ ("I am no longer interested in working with things like ffmpeg/wayland/GNOME's screencaster or solving the issues related to them or why they don't work").MaartenBaert/ssr#431 ❌ broken since, no resolution ("I guess they use a non-standard GNOME interface for this").Wayland breaks screen recording applications Or force more Red Hat/Gnome components (glib, Portals, Pipewire) on everyone! DO NOT INSTALL WAYLAND! Let Wayland not destroy everything and then have other people fix the damage it caused. And usually it stays broken, because the Wayland folks only seem to care about Gnome, and alienating everyone else in the process. Wayland solves no issues I have but breaks almost everything I need. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better of not using Wayland at this point. Tl dr: Wayland is not ready as a 1:1 compatible Xorg replacement just yet, and maybe never will.
