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 36 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...