Think twice before abandoning Xorg. Wayland breaks everything!
tl;dr: Wayland is not ready as a 1:1 compatible Xorg replacement just yet, and maybe never will. 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.
Wayland solves no issues I have but breaks almost everything I need. And usually it stays broken, because the Wayland folks only seem to care about Gnome, and alienating everyone else in the process. DO NOT INSTALL WAYLAND! Let Wayland not destroy everything and then have other people fix the damage it caused. Or force more Red Hat/Gnome components (glib, Portals, Pipewire) on everyone!
Please add more examples to the list.
Wayland breaks screen recording applications
❌broken since 24 Jan 2016, no resolution ("I guess they use a non-standard GNOME interface for this")
❌("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")
❌broken since at least 7 Mar 2020. ("I have now decided that there will be no Wayland support for the time being. Reason, there is no budget for it. Let's see how it looks in a year or two.") - This is the key problem. Wayland breaks everything and then expects others to fix the wreckage it caused on their own expense.
❌broken since at least 7 Mar 2020. ("Wayland is unsupported at this time", "There isn't really something that can just be easily changed. Wayland provides no capture APIs")
- There is a workaround for OBS Studio that requires a
obs-xdg-portalplugin (which is known to be Red Hat/Flatpak-centric, GNOME-centric, "perhaps" works with other desktops)
Wayland breaks screen sharing applications
❌broken since 3 Jan 2018
❌broken since 24 Jan 2016 ("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.
- https://github.com/flathub/us.zoom.Zoom/issues/22 Zoom
❌broken since at least 4 Jan 2019. ("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"). No word about non-GNOME!
Wayland breaks Gnome-Global-AppMenu (global menus for Gnome)
❌broken since 24 Aug 2018 ("because the lack of the Gtk+ Wayland support for the Global Menu")
Wayland broke global menus with KDE platformplugin
https://blog.broulik.de/2016/10/global-menus-returning/ ("it uses global window IDs, which don’t exist in a Wayland world... no global menu on Wayland, I thought, not without significant re-engineering effort"). KDE had to do additional work to work around it. And it still did not work:
❌broken. ("When using the Plasma-Wayland session, the global menu does not work.")
Wayland breaks global menus with non-KDE Qt platformplugins
❌broke non-KDE platformplugins. As a result, global menus now need
_KDE_NET_WM_APPMENU_OBJECT_PATHwhich only the KDE platformplugin sets, leaving everyone else in the dark
Wayland breaks AppImages that don't ship a special Wayland Qt plugin
❌broke AppImages that don't ship a special Wayland Qt plugin. "This affects proprietary applications, FLOSS applications bundled as appimages, FLOSS applications bundled as flatpaks and not distributed by KDE and even the Qt installer itself. In my opinion this is a showstopper for running a Wayland session." However, there is a workaround: "AppImages which ship just the XCB plugin will automatically fallback to running in xwayland mode" (see below).
Wayland breaks Redshift
❌broken ("Redshift does not support Wayland since it offers no way to adjust the color temperature")
Wayland does not work for Xfce?
Wayland does not work properly on NVidia hardware?
- Chris Titus Tech: Wayland vs Xorg https://www.youtube.com/watch?v=U_MBJcD3SFI