- cross-posted to:
- linux@lemmy.ml
- cross-posted to:
- linux@lemmy.ml
This merge resquest has finally been merged into XWayland, which means NVIDIA users are just one beta driver release away (May 15th) from probably having a good experience on Wayland now!
It’s definitely a large leep, but it’s not going to solve everything. I’d say it brings us to ~85% completion. There’s still a lot of smaller issues in need of fixing, and some issues unique to specific problem cards. Nvidia needs to put in that last 10% and the community needs to put in that last 4%. The 1% are the tiny bugs spread across the ecosystem that’ll get fixed overtime.
Nvidia shouldn’t need to put anything in. It’s entirely Waylands fault that it does not work well with the already existing hardware and drivers environment.
Nvidia is shit for so many reasons but not because Wayland doesn’t work well with it.
Nvidia’s failure to implement the spec correctly is solely their own.
Its not the car manufacturers failure when the road is broken.
It’s the car manufacturers failure when they can’t properly put their tires on to safely drive on the road or put on tires that weren’t up to code to begin with.
If Nvidia had worked together with Wayland devs from the beginning this wouldn’t be an issue
Did they worked together with X11 to the same extend they need to work together with Wayland?
If Nvidia had worked together on Xorg, we wouldn’t have had all of those shitty Nvidia unique x11 bugs with Nvidia’s crappy proprietary drivers in the past.
Cannot confirm any Nvidia unique X11 bugs since everything works perfectly fine since a decade or so for me – but tons of Nvidia unique Wayland bugs (same driver version and same card). I am not quite sure if Nvidia are really the bad one in this specific case.
My whole
invironment
is full of stuff to make Wayland actually work with Nvidia.Not one single line of configuration is used for X11.
Here’s just a tiny fraction of the Nvidia specific bugs on X11 :
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/380
https://bbs.archlinux.org/viewtopic.php?id=283461
https://forums.developer.nvidia.com/t/16-bit-overlays-broken-with-x11-and-4xx-series-driver/128067
https://bugs.kde.org/show_bug.cgi?id=460341
You’re using a WM bud, wtf do you expect?
I expect it to work, like Openbox works on X11.
You miss the entire point of WMs then.
You’re complaining about 5 lines of configs when the entire point of WMs is for you to literally customize everything through configs.
Shit, you probably don’t even need half of that crap.
QT_QPA_PLATFORM=wayland
is already handled by qt, you only need that when running apps across Waypipe from a headless server environment. By default QT infers your environment from$DISPLY
which is always:0
in Wayland.