I am aware of the fact that the problems relate to waiting for Wayland to implement features to provide parity with X11. But, with several major distributions announcing that they intend to remove X11 completely from their repos in the next major version or two I would not be entirely surprised if support for it starts to be dropped in other places too, regardless of what anyone thinks about Wayland or their approach.
At any rate, the comment from @dsa-t clarifies that I’ve (not surprisingly!) misunderstood what that line in the release notes means, so no major change for now…
The article is a bit scary, but all this is for a few years, the smooth transition x11 is with us for a long time. It is still not very clear how crutches such as XWayland work in this transition?
I have been using KiCad on Wayland via the XWayland compatibility layer since Wayland became the default session on Fedora (I want to say around 18 months/2 years?) PCB design isn’t my full time job and the most complicated things I do would be around six layer, several hundred up to maybe 1000 components, and I don’t find the limitations too onerous. If I was doing bigger, more complex projects full time, it might be annoying enough for me to have a dedicated X11 session or dual boot another distro for when I’m using KiCad but for general/moderate use I find it to be fine.
That said, I still really want to see full native support sooner rather than later, so I encourage everyone to go and create a gitlab account and upvote the Wayland issues/features listed here:
(To be clear, upvote on the linked issues in the Wayland and wxWidgets projects, not upvote the issues on the KiCad project. Though, upvote those too!)