Here's two to start the thread. I only mention if because this month's release of Fedora 40 is full-on Wayland, no X11.

1. Wacom. The Wacom brain trust has no plan to implement mouse tracking of the Intuos Pen.

2. FlightGear. Any external view when dragged around to the front looking back upon the aircraft, flips the axis so instead of the seamless move the front as in X11, the image goes wacky, underground looking up, move a little, flip again.

Here's hoping that is all there are lurking to baffle Wayland.

Wait until you see the new Wayland with the new sync code. It makes behavior on Nvidia amazing!

Please remove the easy2boot.com links in your sig (only advertising).

I will. It looks like the domain has been abandoned or lost to scammers/squatters.
Too bad, it is (was) a NICE utility!

My local fork of twm is not ready for wayland. I'm proceeding at a snail's taste, so I'd say it never will be. My long term goal is to learn wlroots and its common lisp binding, cl-wlroots, to write a wayland compositor for myself for slackware (and for netbsd whenever it can run it).

So if this really does turn out to be a turning point where you must migrate, I'm in a bind, in that I've lost all enthusiasm for anyone else's idea of what a window manager / compositor should be, while making my own is one of many hobby projects that are dragging out over the years and decades.

But I no longer resent wayland. This guy Rob on the untitled linux show podcast is gung ho for it now (got religion last year I guess), and I'm quietly part of the Rob fan club. This has helped me make my peace with wayland.

I am currently running Manjaro, using PLASMA on Wayland (I also have X.Org installed so i can switch anytime I want). My GPU is Intel. It runs fine here.

I pulled package updates yesterday, and part of what came down was X.Org updates (server, for one). X.Org is not dead or even close to it.

For those running NVIDIA it been hard going for graphic games (I most run DOS games under DOSBOX), but the new SYNC code in Wayland (Provided in cooperation with NVidia) will fix that up nicely.

If I were still running Slackware, I would be running X.Org and happy with it. I see no reason to jump ship on X.Org just because there is a newer and better solution. IF you run slack, it should be because you value stability more than the latest bells and whistles!

This sounds like the mouselook issue.

A lot of games implement mouselook by making the pointer invisible and moving it to the center of the screen. Each frame the game will measure the distance between the pointer and the center of the screen, translate that into a camera rotation and snap the pointer back to the center.

If something happens with mouse positioning or the timing is off, you can wind up with the camera suddenly pointing to the ceiling. I have to build Wine without the user32-rawinput-mouse patches to make FFXIV behave itself.

Obviously I must provide my own DEs but Slackware fully supports Wayland and it's technologies. You need to add your own wlroots and other compositors but sway, hyprland, gnome, and anything else I throw at Slackware works and runs great.

Just because slackware hasn't adopted all these things doesn't mean slackware can't support them. I exclusively use Wayland on my Slackware boxes (and also almost exclusively run slackware) but Slack is as Wayland ready as the next distro. I wouldn't say drop x11 because there's so many things that will never get Wayland treatment, but you can live in the future or the past on slackware.

[footnote: I should point out I run current, things work on 15 but I'm too version limited there.]

1 members found this post helpful.

I liked using Cairo Clock (but doesn't work on Slackware-current) for X but since it's for X it might not work for Wayland at least without that server that converts stuff from X.