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.

I just need steam\proton\wine to support native wayland and then I’ll remove xwayland from my system, can’t wait

i’m on hyprland though

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

I’m using Wayland right now, but tentatively.

Right now there’s an issue in WoW where sometimes when I move my mouse and left-click, the camera jumps to a different position, usually trying to look up.

Only happens on Wayland and it’s fixed temporarily by switching between windowed and fullscreen mode. The problem comes back sometimes when alt-tabbing and refocusing the game.

There was a bug in KDE recently where some menus weren’t properly appearing on Wayland, but that seems to have been fixed after my latest update.

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.

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.

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

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

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

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.

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.

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.