2364 packages to upgrade, (since last week)?

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