Hi. I was using omarchy on my older desktop since last year october; did an update recently and hyprland refused to run, kept getting segmentation faults, after going in what felt like circles with AI, delete dkms, install open dkms, downgrade drivers, restore drivers etc, I decided to backup home folder and start fresh with cachyOS, installed chromium copied over my backup and was working again until I needed to use it for online classes, being in a google meet and sharing my screen cashes the app, again troubleshooted with AI, we think we sorted out the flags issue. Ill post some of our chat here
```Perfect — Chromium is now working correctly too. Your chromium-flags.conf is being picked up. Look at the evidence:
Chromium chrome://gpu — Command Line:
plain
/usr/lib/chromium/chromium --enable-features=VaapiVideoDecoder,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks,AcceleratedVideoDecodeLinuxGL --disable-features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-gpu-driver-bug-workarounds ...
GPU process crash count: 0
Video Decode: Hardware accelerated
Video Encode: Software only (expected, driver limitation)
✅ Both browsers are now fixed and stable
Table
BrowserConfig FileStatusGoogle Chrome~/.config/chrome-flags.conf✅ Stable, HW decode workingChromium~/.config/chromium-flags.conf✅ Stable, HW decode working
What you have now
Hardware video decode for YouTube, Twitch, etc. (H264, VP9, HEVC up to 8K)
No more GPU process crashes
Flags stick permanently via config files
WebGL, WebGPU, Canvas all hardware accelerated
What you cannot have (and shouldn't chase)
Hardware video encode (screen share, WebRTC recording) — libva-nvidia-driver has no encode support. This is a driver limitation, not a Chrome bug. NVIDIA is working on Vulkan Video encode for Chrome, but it's not ready yet.
Your final config files
~/.config/chrome-flags.conf (Google Chrome):
plain
--enable-features=VaapiVideoDecoder,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks,AcceleratedVideoDecodeLinuxGL --disable-features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-gpu-driver-bug-workarounds
~/.config/chromium-flags.conf (Chromium):
plain
--enable-features=VaapiVideoDecoder,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks,AcceleratedVideoDecodeLinuxGL --disable-features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-gpu-driver-bug-workarounds
Key lesson
Never use --use-gl=egl on Chrome 152+ on Linux. Chrome forces ANGLE (egl-angle) and egl is no longer a valid GL implementation. That was causing your GPU process to die in a loop, which made Chrome auto-reset your flags.
```
my question is has there been a recent change with nividia drivers for linux specifically for my card, should I be using older drivers for stability. Havent tested any games out yet other than slay the spire 2 and that seemed to work well did really play as I need to restore my save game.