Absolutely none. On my setup everything runs fine either natively or with Xwayland.

AwesomeWM, and xdotool.

That's it. Oh and x-eyes of course

XFCE, mostly.

RustDesk (remote desktop control) and Barriers (KVM-like server to control my laptop screen from my desktop just by moving mouse to that screen). Both of these are tightly integrated in my daily workflow and would be a hard loss.

There's a modern fork of Barriers but I haven't been able to get it working cross-platform yet. I know RustDesk is actively working to complete wayland support, but it's not quite there yet.

The inability to roll windows up into just the title bar, or to get Firefox to place each of its windows on the same virtual desktop as before, are major annoyances. Otherwise, Wayland runs better than I expected.

GPU screen recorder, the hotkeys dont work in Wayland

autokey

I accomplish the same thing with compose sequences, and by binding a keyboard shortcut in my desktop to call a script with wtype. It's not a cross-compositor solution though, as you'd have to manually setup binds in each of them.

I don't see much hope for this one-to-one unfortunately.

I need to force keepass and some other things to x11 mode so that autotype and window detection works.

RDP.

Stumpwm. The most ergonomic tiling window manager I know, fantastic configurability like emacs.

Talon voice.

Autokey.

Anydesk. (although rustdesk is probably going to replace that)

Talon voice though. I'll need X11 for the rest of my life.

Wayland's been my daily driver for a few years now, mostly without incident. However, occasionally certain applications (Ryujinx and pcsx2, predictably) require the GDK_BACKEND=x11 environment variable to be set before they'll function.

XMonad

urxvt, bspwm, sxhkd, and many small utilities that I built my desktop with. It's hard to reproduce the same setup.

keepassxc's autotype

also, nvidia

Every time I build a new box or do an upgrade, I try selecting Plasma on Wayland from the login screen. Every time it doesn't work, I select X11, and never think of it again for another six months to two years.

Couldn't use xset to manually set some monitors to standby So I searched how to change it back to X.

Also you couldn't set display variable to another computer's ip address (a windows one running xming)

Glxgears. :P I'm on wayland for a least 4 years

For me is the lack of virtual displays is Wayland.

I'm using a 49" monitor (with i3) and split it into virtual monitors/displays. For some tasks two displays are good, for others three, and all doesn't need to be the same size.

The reason for not using i3 splits is that many programs have fullscreen functions that I often use.

Watching a movie is one example, where I have a script that automatically calculate the optimal width without borders and gives me an extra virtual display beside with whatever's left.

Xfwm. Taskbars are now wayland, but don't autohide without the compositor supporting it.

Gnome. No shell restart on wayland, and not planned.

Session restore