- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
You must log in or register to comment.
I accidentally got switched to Wayland after a recent KDE update on Arch, it is better and I’d like to switch to it. I can’t until Autokey and pyautogui work in Wayland. I saw someone else in that thread complaining about TeamViewer but TeamViewer might be working in Wayland.
https://www.kicad.org/blog/2025/06/KiCad-and-Wayland-Support/
After reading this recently, I’m really skeptical about the future of Linux, since everyone seems to be jumping on the train. Are all the people using Wayland arranging their windows every time a program launches, or running a tiling WM?
On my HTPC I have similar problems, Ubuntu is looking to retire X11 support but I rely on an app that allows me to use my smartphone as an input device. Any replacement I see working with Wayland (i.e. literally getting new hardware that would be kept near the TV) would be a downgrade.
I don’t really use applications with multiple windows and Wayland seems to remember the window size and place it in the center which works fine for me.
but I rely on an app that allows me to use my smartphone as an input device.
What sort of input device? KDE Connect can use your phone as mouse/keyboard (and much more).
I think most people don’t use applications that have multiple windows. The trend in GUI design has been towards single window interfaces for quite a while now, so people just don’t run into these issues most of the time.
Why still use WordPress when KDE has its own blog?
Can you guys make a blog account to one of the most known KDE people that he can write his personal opinions there? This post really should be on kde.org.
Gonna be down voted to oblivion, but doesn’t matter, here goes:
Rgarding x11, this is a shame that it hasn’t been dropped already. Investing time and effort into a sad story instead of investing into improving Wayland session and apps. This kind of behavior is known in the corporate environment as sunk costs.
It’s a shame that KDE is always a follower given a huge advantage in Qt toolkit.
I’m not sure how much actual effort it takes to make sure Plasma keeps compiling for X11, but based on the wording from the blog post it sounds like they’re exerting pretty much as little effort as possible. I would say with the recent uptick in leading-edge distros moving to Wayland it’s only a matter of time before almost no one is left on X11, which will deprioritize it even further. Pulling the plug on X11 today is premature given how many people are still running it (SteamOS uses it by default, for example), but I think their ~2 year estimate sounds about right for letting off the gas and putting a hard stop on support.
Any effort in this area is too much since it is for sure wasted. Even Bugfixes. If people want to use it, they should have stuck with plasma lts or use an lts distro.
I know I’m not majority with this opinion, but plasma 6 should have dropped x11. Plasma 7 should drop xwayland.
Not only does this make sense effort wise, but it prioritizes future and not past development.
Valve can stay with older kwin version and/or support move to Wayland with SDL improvements and whatever else is needed. Not that they lack resources… Also Vulkan.
