In general, it’s things that Wayland chose not to do so as to have a better security model.

For instance multi window apps can’t tell the compositor where to put their windows such as snapping a window to another or following a window. Apps can’t read other windows. It’s a good thing for security but it breaks some older tools and workflows.

There’s others like multiple mouse cursors, registering global hotkeys, overscan correction etc but many of these things are being addressed and new standards are being drafted, it just takes time.

I moved to Wayland very early on and, honestly, I’ve not had any problems but I don’t have a complicated or special setup.

For me it's Steam Remote Play. I can't say Wayland is unable to do it, but it's always been so problematic I switch back to x11.

Can Wayland do ssh -X?

Unless I'm mistaken, Wayland can't rotate your display by 22 degrees.

Talon Voice and other accessibility tools like cursorless. I am destroying my hands because I can't do handless input on Wayland.

My personal bugbear is that there is no compositor-agnostic way to tell what workspace a window is located on. This means that taskbars cannot implement an "only show windows on the current workspace" setting, which frustrates me to no end. (Taskbars like the LXQt and XFCE panels still have the setting, but it does nothing.) There is not even any proposed protocol to support this, and acceptance and implementation would take years even if there were.

Integrated desktops like KDE probably roll their own custom implementation, but out in Labwc land I'm shit out of luck. (1 2 3 4)

Automated window positioning through tools like wmctrl and xdotool. There are replacements on Wayland but they're either missing features or are tied to a specific window manager.

I use Xfce, and I like writing bash scripts that can work anywhere.

Support for stylus / pen writing on screen.

AFAIK, there is currently no real equivalent for xrandr on any Wayland compositor.

Normally, you override the EDID rather than specifying modelines manually. Sway also has some limited custom resolution support, but it's just resolution and refresh rate, and not precise timings. Apparently the DRM backend supports modelines but that's not really Wayland by my understanding, more like Steam's gamescope mode.. Actually, the DRM backend is the default backend, so it should work. The other backends are used when sway is run inside another compositor.

I’ve also noticed that Grsync’s password prompt is broken on Wayland.

Forcing XWayland may help here. Otherwise, I assume the application is run as root which generally causes some issues with Wayland but potentially can be made to work.

input-remapper-gtk is a decidedly non-obvious way of rebinding mouse buttons.

Of course, xmodmap is also a decidedly non-obvious way ...

• Run Birdtray
• Not obnoxiously throw up W whenever it can't find an icon for a program during alt tabbing
• Not need extra extra handholding to run games properly without diagonal tears

Eyy, fellow EndeavorOS enjoyer! It's been super solid since I installed it in like April of last year.

Run the old login credentials stealers

Show me a Wayland screensaver. I'm honestly interested if one actually honestly exists.

There are a few things that don't work very well, mostly to do with multi window apps and how some older apps need to run through XWayland (which 99% of the time it works brilliantly! There are a couple weird issues, but most of those are easily fixable through some command argument before opening an app)

I an also running EndeavourOS (which is awesome!) with Niri + Noctalia (which also uses Wayland), and I have no issues :D

So, just discovering the joys of virtual monitors available in the kernel now. NAS now has and gives me sunshine. Bazzite lets you put your own monitors' (ujust setup-sunshine - Configure Virtual Monitor) edid into initramfs so sunshine (and KDE remote access if you want laggy but cut and paste enabled) work without a monitor connection (or dongle), very cool. Just thought I should spread the news and this is vaguely associated.

Not really relevant to the X11 question, except that it provides a (superior) workaround for some issues..

To the actual question, xtool for automating UI stuff hasn't been completely replicated, but given it's an insecure horrible solution I'm OK. Also running a program through a remote connection on a beefier machine was useful at times, is there an equivalent other than remote access?

A lot of 3d software has problems with tablets on Wayland. Stuff like ZBrush, Substance Painter and even their recent AI clones:

• https://github.com/storytold/texturecraft/issues/153
• https://github.com/Aalzard/subcraft/issues/82

Forcing vsync on the pointer is my biggest gripe with Wayland right now. (this has a latency cost which is quite perceptible with a gaming mouse, even with 250hz)

AFAIK, there is currently no real equivalent for xrandr on any Wayland compositor.

What do you mean? Over half of the wayland WMs can use wlr-randr at least that is working decently well.

Run on older video cards.

My home server has a basic Quadro K420. Since the latest KDE forced it onto Wayland, it's unusable even for the short remote sessions I need the GUI for. Chrome hangs if I don't disable HW acceleration, within minutes Firefox leaks memory to the point where the kernel panics, Transmission's window gets garbled like I'm watching a coded PayTV channel.

Installed xfce and everything is back to normal. Of course nVidia shares some of the blame here, but it's clearly working on one windowing system and not on the other.

Drag & drop, cut n paste, and screen-recording are very iffy, even though they technically work.

Just wanted to point out that you can create custom resolutions on wayland with kscreenctl (or kscreen-doctor.) I use it to create to enjoy the enlightened 2880x2160.

Honestly so many tiny annoyances I used to have with x11 have just gone with Wayland. Multi monitor especially seems so much easier to work with.

Just looking at these comments, and the fact that wayland still isn't as good as x11 after all these years (10, 15?) And all this budget shows that wayland is architectually wrong and will never be actually good.

Any software engineer will understand this. If your project is still in basically beta after more than a decade and that much budget, and it's only selling point is that "but it's slightly better than the decades old legacy system", that project has been architectually wrong, and also definitely has awful management, and you call it failed.

Switched my HTPC from a regular Debian desktop with X11 to Plasma Bigscreen (Fedora) with Wayland. Biggest frustration I have is Kodi can't automatically adjust the TV's fps, but besides that it's been going smooth. Steam Link even works well for streaming games from my PC!

Vibe coded a Kodi addon that actually changes the fps, but if anyone knows an actual solution that'd probably be better.

Work with Pynput