A new Wayland protocol is in the works that should support screen cutout information out of the box: https://phosh.mobi/posts/xdg-cutouts/ Hopefully this will be extended to include color information whenever applicable, so that "hiding" the screen cutout (by coloring the surrounding area deep black) can also be a standard feature and maybe even be active by default.

▲

gsora 17 hours ago | parent [-]

Wayland modularity is the gift that keeps on giving.

▲

imiric 15 hours ago | parent [-]

You can't be serious. Wayland is the opposite of modular, and the concept of an extensible protocol only creates fragmentation.

Every compositor needs to implement the giant core spec, or, realistically, rely on a shared library to implement it for them. Then every compositor can propose and implement arbitrary protocols of their own, which should also be supported by all client applications.

It's insanity. This thing is nearly two decades old, and I still have basic clipboard issues[1]. This esoteric cutouts feature has no chances of seeing stable real-world use in at least a decade from now.

[1]: https://bugs.kde.org/show_bug.cgi?id=466041

▲

samiv 15 hours ago | parent | next [-]

Shh...you're not supposed to mention these things alas you be down voted to death.

I also have tremendous issues with Plasma. Things such as graphics glitching in the alt+tab task switcher or Firefox choking the whole system when opening a single 4k PNG image. This is pre-alpha software... So back to X11 it is. Try again in another decade or two.

▲

cosmic_cheese 14 hours ago | parent | next [-]

YMMV and all, but my experience is that Wayland smoothness varies considerably depending on hardware. On modernish Intel and AMD iGPUs for example I’ve not had much trouble with Wayland whereas my tower with an Nvidia 3000 series card was considerably more troublesome with it.

▲

samiv 14 hours ago | parent | next [-]

As a user...why would I care?

If my Ferrari has an issue with the brakes and I go to my dealer I don't care if the brakes were by Brembo.

Blaming the vendor and their drivers is just trying to shift the blame.

▲

cosmic_cheese 14 hours ago | parent [-]

Generally true, though this particular case is due to a single company deciding to not play ball and generally act in a manner that's hostile to the FOSS world for self-serving reasons (Nvidia).

	▲	samiv 13 hours ago \| parent [-]
		I don't even think it's even that. These bugs seem like bog standard bugs related to correct sharing of graphics resources between processes and accessing with correct mutual exclusion.Blaming NV is likely just a convenient excuse.

▲

bigyabai 13 hours ago | parent | prev [-]

> my tower with an Nvidia 3000 series card was considerably more troublesome with it.

I think you're describing a driver error from before Nvidia really supported Wayland. My 3070 exhibited similar behavior but was fixed with the 555-series drivers.

The Vulkan drivers are still so/so in terms of performance, but the smoothness is now on-par with my Macbook and Intel GNOME machine.

▲

imiric 14 hours ago | parent | prev [-]

The thing is that I'm not experiencing this clipboard issue on Plasma, but on a fresh installation of Void Linux with niri. There are reports of this issue all over[1][2][3], so it's clearly not an isolated problem. The frustrating thing is that I wouldn't even know which project to report it to. What a clusterfuck.

I can't go back to X11 since the community is deliberately killing it. And relying on a fork maintained by a single person is insane to me.

[1]: https://old.reddit.com/r/hyprland/comments/1d4s9bw/ctrlc_ctr...

[2]: https://old.reddit.com/r/tuxedocomputers/comments/1i9v0n7/co...

[3]: https://old.reddit.com/r/kde/comments/1jl6zv7/why_does_copyp...

▲

samiv 14 hours ago | parent [-]

Re X11 maintenance... I think it's mostly "done" and doesn't really need a lot of work. So not sure I see a problem there.

	▲	imiric 37 minutes ago \| parent [-]
		Far from it. The recent XLibre release[1] has a long list of bugfixes and new features. Besides, isn't the main complaint from the Wayland folks that X11 is insecure and broken? That means there's still a lot of work to be done. They just refuse to do it. To be fair, X11 has worked great for me for the past ~20 years, but there are obvious improvements that can be made. [1]: https://github.com/X11Libre/xserver/releases/tag/xlibre-xser...

▲

zamadatix 11 hours ago | parent | prev | next [-]

How can Wayland be the opposite of modular and too extensible at the same time?

	▲	imiric 21 minutes ago \| parent [-]
		Because one property doesn't guarantee the other. A modular system may imply that it can be extended. An extensible system is not necessarily modular. Wayland, the protocol, may be extensible, but the implementations of it are monolithic. E.g. I can't use the xdg-shell implementation from KWin on Mutter, and so on. I'm stuck with whatever my compositor and applications support. This is the opposite of modularity. So all this protocol extensibility creates in practice is fragmentation. When a compositor proposes a new protocol, it's only implemented by itself. Implementations by other compositors can take years, and implementations by client applications decades. This is why it's taken 18 years to get close to anything we can refer to as "stable".

▲

codedokode 10 hours ago | parent | prev | next [-]

Isn't this something KDE-specific and because of using third-party program to manage clipboard? On Gnome, there is no Klipper and copy-paste works.

▲

MarsIronPI 15 hours ago | parent | prev | next [-]

You can see the same problem in the XMPP world, with a lot of the extensions implemented only by a few applications. But at least most XMPP extensions are designed to be backwards-compatible with clients that don't support them.

▲

IshKebab 12 hours ago | parent | prev [-]

Omg I thought I was going senile... copy & paste not working... I definitely pressed ctrl-c didn't I?

Bloody Wayland.