Debian

… is not something you should ever use on a desktop PC. Due to its eternally very outdated nature and not even shipping bugfix updates**** it is not a good fit for anything but servers.

Wayland, for some reason, couldn’t handle 4 monitors, with one above the other three.

“Wayland” doesn’t handle monitors at all. What (because of Debian, wildly outdated) desktop did you use?

Oh, and the biggest issue I had with Windows was copied straight into Linux. I want my (single) taskbar on a monitor that isn’t my primary.

Not a Linux issue, but a problem with the desktop environment you chose. KDE Plasma allows you to configure panels in any way you want.

That is not NATO starting any war, anyone wirh the reading comprehension of a six year old understands that. Don’t fall for Russian propaganda, FFS.

How are you taking the screenshots? Spectacle might not capture HDR highlights well, but it should look all proper on SDR content

Multi monitor VRR has never been problematic in Wayland, but the NVidia kernel driver doesn’t support it at all yet, Xorg or Wayland doesn’t matter.

There have been incidents involving malicious code downloaded through Plasma global themes.

No malicious code was involved, just buggy code.

KDE did bother, this does neither happen with KScreenlocker, nor do non-screenlocker windows show in another way, because the screen locker is integrated with the compositor.

If the compositor crashes or gets disabled somehow ofc though, that integration doesn’t help either and you have to rely on a mountain of bad hacks as well as the hope that the screen locker doesn’t also crash for nothing to happen in that case, but it’s as close to secure screen locking as you get on Xorg… in the end the solution for secure screen locking is still Wayland.

the fact that 1.8 was working tells me that it is possible for a window manager to work well for nvidia

Nope, it’s a race condition for which the visible effects can appear or disappear for plenty of reasons. The only fix is explicit sync, which is being worked on for wlroots

It’s been possible for a long time, but yes, now you can do it intuitively in the shortcuts GUI

I am talking about the desktop. Mobile doesn’t have a system tray.

When you have a Xwayland app focused, the Plasma panel will have an upward facing arrow in the system tray. If you tap it, the virtual keyboard will pop up

And you cannot invoke it by yourself to type in XWayland applications

Yes you can

The 1 second present timeout still only works for XWayland

Oof, I thought the corresponding MR for Wayland was merged… But it was from Sebastian and after he got into a heated discussion again and started cursing, the MR got closed by someone else :|

realistically unless SDL2, GLFW or whatever engine a gamedev is using handles it for them they just don’t have the time to worry about what GTK, Qt, or XDG shell does

SDL does handle it, but only for OpenGL; it can’t do anything about Vulkan. GLFW doesn’t do anything about it either, so that is pretty annoying.

I believe in the glorious Wayland future… I just wish it would get here a bit faster

Don’t we all. Let’s hope the current upstream approach to fix this issue gets somewhere sooner than later…

Sorry, but Debian stable is a terrible recommendation! They don’t even ship bugfix releases of KDE Plasma… It’s stuck with a months old version that has lots of known and long fixed bugs in it

Debian doesn’t ship bugfix releases of our software. If you want a stable experience in the actual meaning of the word instead of just something that doesn’t change, almost every other distro will be a better choice

Yes. Flathub wants to become a platform where people and companies can sell their software

Thst might change with Flathub’s ambitions to become an actual app store though

No. Some people wanted to change it to that for Plasma 6, but on Xorg there’s apparently no way to make that happen, as the cursor is always decided on by the window you’re hovering over…

What are the not-a-bugs? Things like covering up a Wayland window will block it’s rendering thread indefinitely with no way to detect it happens to handle it. This can lock up some games, or cause you to time out in a networked application. Some Wayland core folks don’t want applications to know if their window is visible or not because it’s mild information about a user’s attention that should be private. Every game dev on the other hand is asking “WTF!?” as it causes their games to break randomly

Please don’t make up what “Wayland core folks” think. You don’t know it, and your claims are waay off.

It’s not about security. It was intended to allow the compositor to throttle apps to improve efficiency… Which of course in practice doesn’t work like this at all, because OpenGL swap buffers and Vulkan FIFO presentation modes were never intended to be used this way.

As for why that hasn’t been fixed yet, it’s not as big of a problem anymore:

• Mesa (at least for Vulkan) and Xwayland gurantee one frame per second as a minimum refresh rate
• toolkits and libraries use mailbox presentation internally and check frame callbacks themselves for when to render
• xdg shell now contains a flag for apps to know to inhibit rendering because they’re hidden. That doesn’t guarantee that presentation won’t otherwise block though
• a (set of) protocol(s) is being worked on to replace frame callbacks with a mechanism actually suited for OpenGL and Vulkan

Another mild example is that windows cannot be raised except by the user or by launching them. This is supposed to be a mild security precaution so a program can’t pop up a legitimate looking dialog over another application and trick the user. Realistically it means that applications can’t open and focus URL in your web or file browser. Instead they have to give you a notification telling you “Firefox is Ready” and make you do it manually.

That’s not even close to how activation works on Wayland, and no, it’s not just a security thing, it’s a usability thing. Apps can only raise themselves if the currently focused app gives them focus, so that random apps can’t cover up what you’re working on just cause they need to show you an ad or an “important” pop up question or whatever. If it doesn’t work for a specific app, make a bug report about it to the app.

That sounds like your TV is temporarily disconnecting at random, or at least doing something that the GPU detects as a disconnect.

Most likely, AMD’s hotplug detection is too aggressive. You can report that at https://gitlab.freedesktop.org/drm/amd/-/issues

Yes, they did. Neal has been pushing for Wayland by default upstream for a while, and getting that in for Plasma 6.0 was and is the plan.