Steps to reproduce:
-Install Fedora 41 KDE
-Apply all system updates
-Follow the RPM Fusion Configuration guide (Configuration - RPM Fusion)
-Follow the RPM Fusion How to / NVidia guide (Howto/NVIDIA - RPM Fusion)
-Reboot system to apply driver switch
-Install Chrome (doesnt matter if its .rpm or flatpak)
When using the nouveau driver that comes by default, this problem doesnt occur, no matter how many times i resize the window:
I am using the open package with an nvidia 3050 GPU and see no difference than with the closed proprietary driver. Yours may be different since I have had no problems resizing chrome windows with either driver.
I seem to remember a glitch recently while using the proprietary driver [akmod-nvidia] where opening a new tab then shifting it to a new window caused the new window to snap to either the top or side of the screen. I almost never have app windows as full screen. This was just days before I switched over to the open driver.
Note that the akmod-nvidia-open driver comes from the rpmfusion-nonfree-tainted repo so it does not conflict with akmod-nvidia. It also only works with the 4000 and 3000 series (and possibly the 2000 series) cards.
I don’t think that it how it works. The nvidia-open is an nvidia driver that has no proprietary code in the driver itself. All the proprietary stuff is in the nvidia firmware. It is not using nouveau at all as I understand it.
Im using akmod-nvidia, but after your reply, i tried akmod-nvidia-open.
Same behavior…
Just to be 100% sure, i wiped my nvme, reinstalled fedora 41 kde, updated the OS and installed akmod-nvidia-open. Nothing changed. It glitches same as akmod-nvidia.
I dont know if im missing something, doing something wrong or if it really is an issue with nvidia driver / my setup…
That is expected. All the real code is in the firmware which both drivers use.
The nvidia-open is intended to replace nvidia-closed as a 1-to-1 replacement feature for feature.
Digging deeper into the problem, I apparently discovered the cause: Google Chrome was apparently running with XWayland instead of Wayland, which combined with Nvidia proprietary drivers was causing this issue. After forcing the launch with the flag ‘–ozone-platform=wayland’, the problem stopped happening.
For now, I will mark this as the solution. Thanks for the help!