In Bazzite, you should just need to open the Discover package manager and click "Refresh" and then "Update All" in the top right. Although these drivers don't appear to be available through the package manager yet; mine is still on version 560.31.02.
When I first installed Bazzite on my Intel+Nvidia laptop, the Firefox crashes were constant. The workaround here fixed the issue for me.
Thanks. I changed those items in Flatseal and now the Firefox window is a visually garbled mess — very clearly broken like a bad video card. Got any workarounds for the workaround?
Ah, darn. Unfortunately I have no additional help to offer since that particular issue was fixed for me after changing those options in Flatseal.
I'd try running Firefox from the terminal to see what error message you're receiving when the crashes occur; the unique error message was what led me to this workaround when I was originally troubleshooting.
In Bazzite, you should just need to open the Discover package manager and click "Refresh" and then "Update All" in the top right. Although these drivers don't appear to be available through the package manager yet; mine is still on version 560.31.02.
If your Firefox crashes are anything like mine were, it should be solved by opening up Flatseal and disabling Wayland rendering for Firefox. See the screenshot shown here: https://universal-blue.discourse.group/t/nvidia-555-drivers-incoming-important-information/2554
When I first installed Bazzite on my Intel+Nvidia laptop, the Firefox crashes were constant. The workaround here fixed the issue for me.
Thanks. I changed those items in Flatseal and now the Firefox window is a visually garbled mess — very clearly broken like a bad video card. Got any workarounds for the workaround?
Ah, darn. Unfortunately I have no additional help to offer since that particular issue was fixed for me after changing those options in Flatseal.
I'd try running Firefox from the terminal to see what error message you're receiving when the crashes occur; the unique error message was what led me to this workaround when I was originally troubleshooting.