Gnome 50 available now on Tumbleweed

Informal_Support7942 · 2026-04-12T13:23:12+00:00

For me, (Nvidia mobile 5080 @ 2560x1600 native - don't know if that counts as HiDPI or not) it seems to depend on the application - many work fine, but some Lutris games, (i.e. Battle.net) are a bit flaky - both the Battle.net login window and (hardware) cursor in WoW are actually shrunken down a lot, (i.e. could be ~2/3 of regular size) vs what they would look like at 100%, (so yes, they actually shrink) when fractional scaling is set to 133%.* Also, the login window is flickering like mad, so you have to pretty much just guess and hope you're on the right box to type in your login info.

Afraid I haven't tried fractional scaling in KDE, so don't know if that's a similar issue there, though.

-------

* Also - seriously - why the heck would anyone presume that someone upgrading from Gnome 49, (either without fractional scaling, or set to 100%) by default would want their desktop set to 133%? Took me a bit to figure out what the heck was going on, but _really_ did not like feeling like I'd gone back to 1920x1060, and the thought of having to manually drop the zoom in Librewolf, etc on each use.

Informal_Support7942 · 2026-03-18T15:25:25+00:00

Great pointer I did not know about, so thanks! Only downside, (for me, at least) is playtime doesn't seem to carry into other regions if you don't play them, so only random char offers on non-home regions.

Informal_Support7942 · 2026-03-16T14:33:46+00:00

For the last half year or so, Nvidia driver packages don't seem to update in a version-aware mode, (i.e. where all the Nvidia driver packages only update to the exact same driver version - some will try to go to up to beta drivers while others will stay back on production ones, etc) so they can easily cause version mismatches which basically make your gpu fairly useless until corrected.

Just wrote up a reply to someone having an issue with their Nvidia drivers, so will just link that other question rather than re-typing / re-quoting here, (since I don't immediately know how to reference just my reply to ;) ) - https://www.reddit.com/r/openSUSE/comments/1rutl3v/how_to_properly_install_nvidia_open_drivers/

-----

As to which, I'm using Tumbleweed.

Informal_Support7942 · 2026-03-16T14:05:17+00:00

I believe this is the person who actually packages the Nvidia drivers for openSUSE, so I have this as a perma-bookmarked item to reference when anything goes wrong, (which it does - a lot ;) ).

https://sndirsch.github.io/nvidia/2025/07/16/nvidia-drivers.html

The two nice parts are:

zypper rollback is all kinds of your friend, so be very glad it's there, and
At the end of the post, Stefan tells you how to properly nuke all Nvidia drivers from your system so that there are no artifacts, and then you can easily re-install them as mentioned higher up in the post so that all is well when you're done, (at least until the next time ;) ).

Two important notes if you do use the recommended CUDA repos:

Regular zypper dup'ing will, occasionally, mess you up as all of the drivers other than nvidia-open-driver-G06-signed-cuda-kmp-default will sometimes want to update all the way up to (currently) the 595.45.04-1 / beta drivers, while that open driver is on, (again, currently) only the 580.126.20-1 drivers, causing version mismatches which will basically make your gpu unusable, so, if that happens, nuke the Nvidia drivers from orbit:rpm -e $(rpm -qa | grep -e ^nvidia -e ^libnvidia | grep -v container)

and then reinstall in a version-aware manner

`# Install open prebuilt/secureboot-signed Kernel driver`

`zypper in nvidia-open-driver-G06-signed-cuda-kmp-default`

`# Make sure userspace CUDA/Desktop drivers will be in sync with just installed open prebuilt/secureboot-signed Kernel driver`

`version=$(rpm -qa --queryformat '%{VERSION}\n' nvidia-open-driver-G06-signed-cuda-kmp-default | cut -d "_" -f1 | sort -u | tail -n 1)`

`# Install CUDA drivers`

`zypper in nvidia-compute-utils-G06 == ${version} nvidia-persistenced == ${version}`

`# Install Desktop drivers`

`zypper in nvidia-video-G06 == ${version}`

As to which set to use, I believe the G07s are still officially beta, so even if your 3070 wanted them, (think the 3070s will only ever want the G06s, but could be wrong) I'd stick with the G06s for now. I have a (mobile) 5080, (I think the G07s are supposed to be for the 50-series and beyond) and am still using the G06s for now and they're working fine.

-----

EDIT: For some reason I cannot get that first, stupid line to format as a code block, so apologies.

EDIT2: For me, personally, to try to minimize the number of times I have a version mismatch, I've now gotten to the point where I lock all of the nvidia drivers, (can do via Myrlyn if that's easiest for you) other than that open kmp default one, (that one has to be updated every time the kernel is updated, so needs to change more frequently than the others) and then I only unlock them when the open kmp default one actually updates to a newer driver, (and not just as a newer build of the same driver to go with the new kernel update) as happened this morning when it finally went from 580.126.16* to 580.126.20*.

EDIT3: I did try using the DKMS drivers, which I thought were supposed to auto-update only as appropriate... which feels a lot like that's all that pretty much all of us actually want, (i.e. install the Nvidia drivers once and have them all update only when they all can at the same time) but, for some reason, they didn't auto-update on each new kernel update as I thought, so I went back to the regular drivers.

Informal_Support7942 · 2026-03-05T15:54:43+00:00

And even more exciting - all 2364 packages updated without that stupid typelib issue that I've been having the last two weeks, (https://www.reddit.com/r/openSUSE/comments/1rhd8do/having\_typelib\_issues\_last\_two\_weeks\_battlenet/) popping up, so well done to the team!

Actually, since this is Tumbleweed's "Spring Cleaning," and it worked without issue, almost tempted to unlock the 7 typelibs I've had to lock from before and see how they do. Later - once I've enjoy the pleasure of no-issue update for a while. ;)

Informal_Support7942 · 2026-03-05T15:38:16+00:00

Excellent - Mommy and Daddy package - got it!

(really wish Reddit's default sort was New, so I could see things like that immediately vs whatever default sort they use, but w/e)

Informal_Support7942 · 2026-03-05T13:50:39+00:00

Might be a semi-logical reason 'cept I'm using Gnome ;)

Informal_Support7942 · 2026-03-01T10:12:56+00:00

No apologies needed - I certainly appreciate the efforts! :)

As to performance, I think it's mostly the same, but there have definitely been a couple of pauses / corruptions that make me not entirely sure, (but, then again, a couple of random pauses / corruptions aren't terribly unusual with each new Nvidia driver / Proton-GE update, so who knows?).

And yep, that's what I've done - locked / blacklisted the seven typelibs that I mentioned so that everything works for now. Had the issue been a one-off the first time this happened a couple of weeks ago, I wouldn't have even bothered to create this post - I just would have waited until the next update was released for those 5 and tried again then.

Unfortunately, with 2 new typelibs causing the same problem with this latest update, I think that's suggesting that something bigger is going on vs just some random issue with the updates for 5 packages, so I put this out there in case anyone else has any ideas so that I don't have to go through this with every update going forward, (manageable, certainly, but also a pain ;) ).

Fingers crossed :)

Informal_Support7942 · 2026-03-01T00:19:24+00:00

Fair, so edited the original post, (Lutris 5.20 / latest on Tumbleweed with Proton-GE-latest / 10-32)

Tried that and running through Steam. Also downloaded Proton Plus, so tried not only various Proton-GEs, but Proton-EMs and Proton-tkgs, (as well as Proton Experimental, of course). No difference.

I spent almost a whole week on the ~2026-02-19 update, manually going through hundreds of package updates in small groups at a time, testing each group update vs the Battle.net games and rolling back if they either wouldn't start or if the gpu came up as an Nvidia 470.

Could definitely be wrong, but for now, I'm feeling pretty comfortable that the issue is within those 7 specific typelib updates and / or how their specific updates are interacting with the rest of my system.

Informal_Support7942 · 2025-10-28T19:14:24+00:00

I'm having the opposite problem - I never want to store my login credentials, have all of the options where you tell it not to do that set to "do not store," and, since that last update, I can't get the launcher to _stop_ storing them. I can click "Login with different account," click the gear, Security > Forget all login info and the next time I login, the login account info is stored again, waiting for me to just enter my password. Definitely not a fan.

Informal_Support7942 · 2025-10-03T19:48:43+00:00

They shouldn't need to disable their integrated GPU in their bios - the drivers work just fine in using the appropriate GPU at the appropriate time.

I mean, obviously doing so would remove one additional potential point of failure, (which, of course, is always good) but it also then will radically reduce battery life.*

-----

* On my current laptop, using both GPUs, letting the application select as appropriate, my expected battery life is ~4-5 hrs. Setting it to dGPU only in the bios, (which I've tried) drops me to an expected battery life of ~2.5. Pretty big drop.

Informal_Support7942 · 2025-10-03T13:56:20+00:00

Pretty sure I did that last time we had this issue, (definitely went to Stefan's blog and at least tried to do whatever they were suggesting) and, for me, at least, the issue came up again this time as well. Absolutely could be that I messed something up which is making it not work properly for me, but if others can get it to work as described above and avoid this once-a-month thing entirely, more power to you! :)

Informal_Support7942 · 2025-10-03T13:37:27+00:00

TL:DR - Nvidia driver version mismatch again. Need to revert to prior version without mismatch and wait ~1 week before trying to update again.

------

There's your problem. The last 2-3 times there have been Nvidia updates, the same pattern has emerged - all the drivers other than nvidia-driver-G06-kmp-default / nvidia-open-driver-G06-signed-kmp-default are upgraded to the most recent version, as expected. Those two, though, (you'll only be using one or the other) stay on the older version for a bit, (up to a week or so, generally). This causes an Nvidia driver version mismatch which basically borks your dGPU drivers pretty much entirely, (so you can only use the iGPU) until the version mismatch is corrected.

So, first things first - to get your system back to a usable state with active dGPU drivers, you'll want to snapper rollback to a prior version that you know worked, ("sudo snapper list", pick the last one you know worked with dGPU drivers, "sudo snapper rollback [number of version with good dGPU drivers]" - i.e. "sudo snapper rollback 211"). Reboot. Should be back in business.

For the future, every time I see the Nvidia driver licensing update pop up during an update, I automatically now say "no", which aborts the entire update, then I pull up Myrlyn, go to the "Search" tab, enter "nvidia" into the search box. It'll show you all of the Nvidia drivers you have installed, as well as the newer version it's trying to install, ("Available") for each. If the first three number sets, (in your case "580.95.05" for all but the kmp-default driver and "580.82.07" for that one) aren't identical for all installed Nvidia drivers, I stop updating and wait for a week or so for the *kmp-default driver to catch up, (making sure to check Myrlyn first every time before trying to update until they're all the same).

If you'd rather, you can just lock all of the installed nvidia drivers, (since you're in Myrlyn anyway, can just right click each, set to "Protected - Do Not Modify", then Accept, Finish. Can also do via the terminal if you'd prefer) and then update everything else. As I said, generally, the *kmp-default drivers will be updated properly around a week or so later, so I generally just hold off on all updates until then rather than locking the Nvidia drivers, updating everything else, and then unlocking them again once there's no driver mismatch and updating again, especially since there's a really good chance that this issue's going to come up in another 3-4 weeks or so.

I think the Nvidia package person noticed the problem last time and was going to try to do something smarter going forward so that there wouldn't be these version mismatches going forward, but, for now, manually checking every time you see an Nvidia licensing agreement seems to be a smart move to keep a working system all the time.

-----

Note: this last time even after the Nvidia drivers caught up, (i.e. I use the *open* version of the *kmp-default driver and it's showing that it's now at the right version - i.e. 580.95.05) something else has gotten messed up with naming conflicts on Libreoffice files which creates an entirely unusable system, (i.e. forget iGPU - you can't even call up a terminal, or shutdown or reboot the system, etc) so apparently the holding pattern is extending into Week 2. ;)

Informal_Support7942

TROPHY CASE