More Wayland Concerns

I just read a post titled Concerned about the push for Wayland. When I tried to comment, I was told that since it was marked solved, I should start my own topic. So here I am, even though starting my own topic tried to send me back to the post I came from.

My concerns about Wayland are unrelated to the other poster’s concerns. My problem is that it appears to have been released incomplete, and various functionality simply doesn’t work. Maybe it works in current versions of X; maybe it does not. I’m a naive user, not a window manager expert.

Problem 1:

It’s not possible for an app to determine whether or not the user is actively using keyboard and mouse. I understand this to be Wayland-specific, and working on X11. It definitely works on macOS. Reminder-to-take-a-break apps need this functionality, and I need reminder-to-take-a-break apps.

Problem 2:

Session management is essentially broken, for lack of a language for specifying where you want your windows, or recording where they currently are to replay later. Last I checked, Wayland planned to get around to defining such a language one of these days, and once they had, it would eventually be adopted. Meanwhile, users are out of luck because the Wayland developers don’t want to adopt whatever X11 had - which would only handle a subset of what Wayland can do - but at least it would be better than nothing. Why not adopt this in the meantime, and make it a supported subset of their eventual more all encompassing standard?

Problem 3:

If you use non-integral scaling, various apps don’t work right. My aging eyes can’t handle my 4K monitors at their natural resolution. Older systems let me pick from a list of resolutions; on MacOS I run them at 1920 x 1080, rather than their natural 3840 x 2160. Others (some Ubuntu derivative, 2+ years ago) let me scale, but only by e.g. 200%. Both of these give me less resolution than my eyes can handle, but everything works.

Kubuntu installation defaulted to 3840 x 2160, scaled at something like 180%. That’s perfect for my eyes, except random apps don’t work. Broken apps include anything I’ve tried written in java, lots of older steam games that supposedly work on linux, and DOSbox’ graphical tool for configuring keyboard mappings, needed for older software that expects keys that are eaten by your window manager rather than passed through to the dosbox app. (The only solution is to remap something else to the key the app wants.)

FWIW, my complaint here is primarily that the default installation is broken, because it uses functionality that isn’t fully supported. This is a great way to leave users with a general impression like “linux doesn’t work” or “kde doesn’t work”.

If the non-integral scaling were presented as bleeding edge, use at your own risk, perhaps with a nice link to a page of known issues, I’d be far less unhappy with this one. It is, after all, new functionality, rather than something that works in X11.


--

I’m sure there are plenty more examples of things that just don’t work on wayland, or don’t work on wayland with kubuntu (and kde?) default configurations, where the root cause is one or more of (a) wayland isn’t finished, (b) wayland doesn’t do backwards compatibility well or (c) apps people need haven’t been adapted to work with wayland.

I’m unhappy. I don’t really want to use wayland as long as it doesn’t have a fully functioning tool kit.

Obviously part of my problem is kubuntu, not kde, since I gather that even recent kde versions can still work with X11. But I really don’t want to lose functionality in order to inhabit the bleeding edge, however good it will theoretically be once the kinks are worked out.

--

So here’s my ignorant 2 cents worth.

Any idea when I’ll be able to run all my retro games on wayland, or at least all that are runnable on X11? Or when generic java apps that work on MacOS, Windows, and non-Wayland linux systems will work on Wayland/KDE, possibly with the aid of some kind of adapter analagous to DOSBox?

What’s the chance that by that time kde and/or kubuntu will have moved on to something even more bleeding edge, leaving wayland behind?

Not true.

There is a protocol ext_idle_notifier_v1, and other DE-specific ways or not wayland-based solutions.

The protocol has been adopted, it is implemented by compositors, not all apps have support, give it a few more months.

As your phrase imply, that’s an app problem. Fractional scaling is a Wayland innovation for the long run.
They are possible workaround, but none built-in, that’s not great.

That’s on app to modernize their support on Linux/Wayland platform. It will take time.
Until Wayland had become the main target for Linux, those applications had little incentive to update.

You can change your scaling factor when you use those applications.

They should run fine with XWayland, try at least.

Kubuntu does also have all packages needed for X11.
They might not be installed by default though.

If you are on 26.04 it will be available for several more years as that is an LTS version.

That’s good to know. So now I’m waiting for an app that uses the KDE specific solution, and isn’t otherwise unsuitable. Or I could in principle download the source of the app I’m using, which often unhelpfully tells me to take a break the instant I sit down at the computer, and fix it to do the right thing.

FWIW, I tried at least one break reminder app that was part of the KDE suite when I first installed kubuntu, and it not only failed to do this; it was also prone to hanging the system. I’m not sure exactly when, except before 26.04 LTS came out. Maybe 1.5 years ago?

That’s even better to hear. As of when I installed Kubuntu, I figured it would be at least two years before it had the underpinnings to enable mac-like session management, where the system remembers what windows you had at reboot, logout, or crash, and restores them when you restart.

I also figured it probably wouldn’t implement that, but at this point I’d settle for a method of having my standard windows launched automatically, each in the appropriate position in the appropriate virtual desktop. (Last I checked, which was when I moved to Kubuntu from MacOS, what session management KDE had didsn’t play at all nicely with virtual desktops.)

The way I see it it’s a user problem - users have a problem from when the first upstream change is made until all the downstream developers adapt to that change.

Worse, there’s always the fear that the upstream developers will make another breaking change before the first one fully propagates, leaving the users with no chance for a non-broken overall experience.

Also, apps that are no longer maintained never get converted to the new methods.

I haven’t risked this so far. I fear what might happen to anything else I’m running during the switch. More importantly, though, I multi-task. I want e.g. Discord behaving normally even while I’m playing a java-based game.

So far, I’m living without some functionality I’d like (mostly very retro games, and dos box features), and using my ancient Mac for anything written in java.

The dos box problem is solvable in principle by reverse engineering the format of the human readable configuration file written by the broken tool. Unfortunately, the only documentation is the source code, so working around this mess requires more work than I’ve so far been willing to allot to it. Maybe I should try “vibe coding”, since the LLM can presumably read the microscopic display, as well as the file it writes.

Now my ignorance is showing. Is that something I install to replace Wayland, or a behaviour I can configure with the standard Kubuntu installation? If the latter is this something the system settings app can handle, or do I need to handle the problem by editing a configuration file, or using a command line tool.

And yes, I should probably have tried a search engine before asking. But I’m still on my first caffeinated beverage of the day.

To be fair, this is a new feature, so users haven’t lost anything they already had.

It’s not KDE’s fault that Kubuntu uses this feature by default, breaking the user experience until universal adoption happens.

And it’s neither of their fault that I like the feature so much I kept using it, in spite of the unwanted side effects. I could give up the extra real estate, and the improved window size matching between my non-identical monitors, and use the monitors the same way MacOS uses them.

I just looked up XWayland. It looks like I need to install it, if not already present, and figure out how to get the problem apps to use it.

Or maybe not. I’m now finding it’s already present, and can’t do anything about fractional scaling issues.

According to the compatibility matrix the mentioned protocol is available in KWin (Plasma’s compostor) since at least version 6.7

So even software not specifically written for KDE’s desktop could be a consideration.

I think at the moment the missing piece is the system component that tells apps to restore a specific, previously saved, state.

However, apps that have their own session restore should be able to do that on their own when started manually.

Yes, that is one of the main advantages of the new approach.
Applications restore the content of their windows but the window manager restores their state (position, virtual desktop, etc).

These kind of changes are rare due to the effort for all parties involved.
And when they happen they do over a long stretch of time and usually with compatibility measures in place.

Hence compatibility measures, like XWayland in the case of the X11 to Wayland transition.

Shouldn’t be a problem, especially once Java has caught up (Project Wakefield)

A quick search suggests that DOSBOX-X is capable of running natively on Wayland with extra some configuration.
Could even be that it works without that by now, after all the linked finding is from early 2025.

XWayland is the standard X.org Xserver running as a client of the session’s Wayland compositor. Essentially like Xquarz on macOS.

It should be available on Kubuntu by default, or really any contemporary Wayland setup unless it was specifically disabled.
KWin will detect the connect request of any X11 client/app and start XWayland to let it handle that request.

It turns out XWayland is there by default, and there’s a choice in system settings

Legacy Applications (X11)

Apply scaling themselves

Scaled by the system

Info boxes say that all will be blurry if scaled by the system.

There’s no way to tell it to scale only specific named apps, not any X11 apps that are behaving properly, perhaps because they understand such scaling. Nor is there any easy to find way to determine which apps are taking this path.

This might turn out to be the answer to my problems with retro games, rarely used dos box components, and java apps. Or then again, it might give me new problems (blur on currently well behaved apps) for old (unreadably tiny windows on other apps).

I’m currently on the forums as part of working on a different random issue, so will try this after I finish dealing with the current issue. (Not a KDE or Wayland problem. At worst, it’s a doc problem.)