I’m not sure if mobile AMD users have to do the same
No we don’t. Mesa and the kernel automatically decide to use the dGPU for intensive tasks. It is only on rare ocassions that I have to use the DRI_PRIME=1 to force the use of the dGPU. It has been months since I last did it
go mental like Torvalds.
What! I missed Linus going crazy¿? When did this happen¿? Do you have any videos¿?
DId your Nvidia drivers update recently? If yes try the older Nvidia driver
I have got an old shit laptop and I don’t see this. Can you verify this using mangohud¿?
Just for future reference.
KDE NEON is a distribution maintained by the kde community so that you can enjoy the latest and greatest kdqe has to offer on an Ubuntu base.
KDE plasma is a Desktop Environment(DE). It controls the look of your desktop and to some degree how you interact with your computer. You can use kde plasma in almost any distribution. It is somewhat analogous to launchers in android with the caveat that DEs affect a lot of more of the system than launchers do in android.
It has been some time since I tried out Nobara so I might be wrong. I just remember that Nobara page lists having amf encoder support out of the box as a feature
While I don’t know how, I do know that there is a way to have mesa for most things while having AMF encoder for encoding. Nobara has this set up out of the box so there is some way. Maybe you could search for it using a search engine
In the meantime please share that these issues exist on nvidia forums. Issues caused by nvidia drivrers shouldn’t come under the purview of the kde devs.
Yeah I forgot about monitor support. Guess that’s pretty important. But is pixel shifting gnome’s responsibility or should that be done through monitor firmware so that it’s OS agnostic¿?
How are gnome supposed to improve hardware support? Do gnome devs write drivers and such at the present time¿?
I am also sure that it will land as well. As a gnome user I hope it lands sooner than later. I am just frustrated because the pursuit of perfection is keeping us from having a better experience now. It’s the calculator on iPad situation. Just because the perfect solution has not been found yet does not mean there should be no implemented solution at all.
These discussions took place several years ago if I remember correctly. The problem seems to be that cursor seems to want to refresh at a different rate than the content in screen and the people at gnome want the cursor to not feel choppy by being refreshed at the vrr determined refresh rate
VRR does have patches In progress.
This has been the case for years at this point
Wasn’t fedora 38 already on linux 6.5. Why is that touted as feature of fedora 39¿?
I thought dnf 5 wont come with fedora 40 because that coincides with the next RHEL release so they want both of them to ship the stable and tested dnf version.
edit - FedoraProject confirming that F41 is the target for dnf5
Well for me it auto updates and stages in the background. There is config file /etc/rpm-ostreed.conf in which you can set the AutomaticUpdatePolicy to stage. Then it will automatically check for updates once a day(I think) and will download and stage it. The update is then applied when you shutdown or reboot
Why did you find the need to use the rpm-ostree command¿? Isn’t the purpose of immutability to use flatpaks and containers to get all your apps/software
I am guessing all of them is it was game running through proton
Edit : the game seems to have a linux native version
The gap between 6.5 launching and 6.6 launching seems smaller than normal.
Edit : looking back this is not the case. It is the same 2 months between releases. Man time flies
This is Top tier sarcasm!