As a developer with a Linux laptop (ThinkPads, etc.) since forever, I have been avoiding nVidia like the plague since switcheroo became a thing more than a decade ago. Every time I tried the user experience with (discrete) nVidia cards as a non- single screen gamer has always been a horrible waste of battery. Intel and AMD GPUs getting so much better have been a total blessing. Being able to just connect an external monitor/projector with different scaling without a hassle is very liberating in a professional setting

I think it should be a point of pride for the linux developer community that nvidia cards work as well as they do seeing as the company is actually hostile.

The only solution for the end user is to vote with their wallets if running linux and/or wayland is important to them.

Bringing it as an argument _against_ wayland, however, is missing the point entirely in my opinion.

Well the bug that I’m experiencing is specific to Xwayland and seems to be a bug where the wayland developers are refusing to take Nvidia’s patches to fix the issue. So maybe it is wayland and not the drivers? Nvidia and Google seem to have a decent relationship working together to resolve issues for Linux Chrome Wayland.

what patches and why?, the other two major gpu company (intel and amd) don't need to send any patch to make their gpu work perfectly on wayland, why nvidia need it?, isn't their fault that their driver system is flawed?

Today Xwayland relies on implicitly synchronization. That’s apparently a legacy mechanism. Nvidia wants to add explicit synchronization support which it has as it sounds like the future whereas AMD and Intel aren’t ready for that. Xwayland devs claim the ecosystem isn’t ready and yet if a simple patch fixes the issue for Nvidia and the Xwayland folks agree eventually GPUs will use explicit synchronization, it seems like the Wayland folks are the ones dragging their feet.

https://indico.freedesktop.org/event/2/contributions/78/atta...

https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...

https://wayland.app/protocols/linux-explicit-synchronization...

On what basis do you make the assertion that intel and AMD don’t contribute patches to wayland or compositors? That seems like an extraordinary claim.

The latest 545 Nvidia driver is so broken that I had to downgrade back to 535. A huge amount of Linux desktop issues can be traced to Nvidia and their drivers.

Maybe although I haven’t experienced issues that appear to be Nvidia driver issues per se (ie I’ve installed older ones and newer ones and all issues remain). I’m on a desktop 2080 so that may be it. Haven’t noticed anything especially bad with 545. What kinds of issues have you noticed?

There's an example right above you of NVIDIA's explicit-sync patches being rejected because AMD and Intel aren't ready to move on that piece of functionality yet, despite implicit sync resulting in higher latency and a worse experience for users, and being generally agreed to be undesirable and not the direction they want development to go, which is generally agreed to be what NVIDIA has implemented. And this follows the overall hostility over EGLStreams or whatever it was.

They're doing the code and releasing the patches, and they largely capitulated on whatever the EGLStreams issue was supposed to be about, they are leading in what everyone involved seems to agree is "the right direction" and the linux community still can't find their way to "yes". At some point you have to start looking at it as not being entirely NVIDIA's fault - "fuck you, NVIDIA" is no longer an expression of how difficult they are to work with, but rather a generalized expression of hostility from the linux community over perceived historical slights etc.

Like, if there's some big history of warfare between IBM and the kernel team, are you just going to reject any patch coming from IBM because you don't like the company, even when it's generally agreed that the patch is generally right and going in the consensus direction, just because you don't like the name on the signoff? That seems to be where the linux community is at these days.

The whole "fuck you, nvidia!" thing has always been noxious, that's an example of linus's personal toxicity that a certain segment of the linux community has eagerly celebrated. At best it is a thought-terminating cliche that contributes nothing and drags down the debate, and at worst it's given covering-fire for that segment to act out in their own immature, negative ways, to the detriment of the users.

It's not a good look, it's just immature, and at this point it's practically expected from the kernel team. Look who's in charge (and it's not just linus, GKH seems pretty bad too, from a casual observer every time I see his name come up it's some childish troublemaking like the symbols-relicensing warfare thing).

My setup:

    * 3 monitors
      * 1x 2560x1440@60Hz
      * 2x 1920x1200@75Hz
    * X99 - Broadwell chip
    * Fedora Workstation 38/39
    * GTX 1070
      * Driver 545 from RPM Fusion
      * Currently on 545.29.06

Workloads:

    * Excessive terminal use
    * Code authoring (VSCode/Vim)
    * Web browsing/app usage in Firefox/Google Chrome
    * Screen sharing and recording (browser/OBS)
    * Electron apps including Slack, Element, and Discord
    * Occasional use of Krita^

^ Krita has a known issue with (X)Wayland, canvas acceleration, and tablet input.

I decided to give Wayland on my workstation another go when the 545 series dropped. Hilariously, the main reason being the underlying features added that enabled support for GNOME's Night Light feature.

Other than the first day of going through my apps and making sure things worked, I haven't had any real issues. For the work I do, Wayland more than covers my needs.

I have gotten a smidgen of cursor glitching after upgrading from the released 545.09.02 NFB driver to the beta-NFB 545.09.06 version. It only happens when GNOME switches to its "loading" cursor, but it's mostly been ironed out by now. I updated the driver as part of the system upgrade from Fedora 38 to 39, so that probably had a hand in causing it.

On my nvidia system (gtx a2000) with an ultra wide monitor and Gnome, Chrome seems to be glitching if I do the following.

- open a new Chrome window

- snap the new window to fill half the screen by dragging it to either left or right edge of the screen

- result: solitaire-like window glitches

- if I resize the window a bit before snapping it, it works.

I haven't seen this glitch on any other app.

Can't say I've seen that one. I have seen Chrome have some windowing issues, but nothing that would drive me crazy. I've also added "--gtk-version=4" to my launcher to support alternate inputs (e.g. typing booster).