Fix Chromium playing video as a black rectangle after an update
The symptom and ANGLE diagnosis are plausible, but the fix flag does not exist and the procedure will break the user's browser. Verified against chromium/chromium ui/gl/gl_switches.cc: the only valid --use-gl values are egl, angle, mock, stub, disabled. There is no 'desktop' value. It was removed. Forcing native GL instead of ANGLE's default backend is --use-angle=gl (valid ANGLE names include default, gl, gl-egl, gles, vulkan, swiftshader). --disable-features=UseChromeOSDirectVideoDecoder is a ChromeOS-only feature flag, is inert on Linux, and does not disable GPU rasterization as claimed. Most damaging: Omarchy SHIPS a populated ~/.config/chromium-flags.conf containing --ozone-platform=wayland, --ozone-platform-hint=wayland, --password-store=gnome-libsecret and --load-extension=... . Telling users to 'create the file ... one flag per line' invites them to overwrite it, which drops Chromium out of Wayland/ozone and breaks keyring-backed password storage.
Symptom
After an Omarchy update, videos in Chromium/Brave/Chrome play as a black rectangle (audio still works), or the browser lags, flickers and jitters badly. The browser log is full of:
SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing
eglCreateImage failed with 0x00003009
OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
Cause
Chromium defaults to ANGLE (egl-angle) on Wayland. A Mesa/Wayland stack bump shipped by an Omarchy update broke the ANGLE -> EGLImage -> DMA-BUF video path on some GPU/driver combinations, so the compositor gets an unusable buffer.
Fix
Force Chromium off ANGLE's default backend onto native desktop GL. The flag is --use-angle=gl, because --use-gl=desktop was removed from Chromium and is silently ignored (the only valid --use-gl values today are egl, angle, mock, stub, disabled).
Omarchy already ships a populated flags file, so **append** to it, never overwrite it. Overwriting drops --ozone-platform=wayland and --password-store=gnome-libsecret and will break Wayland rendering and your saved passwords.
For Chromium:
cat ~/.config/chromium-flags.conf # look before you touch it
echo '--use-angle=gl' >> ~/.config/chromium-flags.conf
For Brave:
echo '--use-angle=gl' >> ~/.config/brave-flags.conf
Fully quit and relaunch, because a background process keeps the old flags:
pkill -f chromium; pkill -f brave
Confirm what actually took effect by visiting chrome://gpu and checking the ANGLE line.
If gl does not help, try the Vulkan backend instead:
echo '--use-angle=vulkan' >> ~/.config/chromium-flags.conf
If you already clobbered the flags file, restore Omarchy's defaults:
omarchy-refresh-chromium
Verify
Open chrome://gpu and the GL renderer no longer reports ANGLE. A YouTube video renders instead of showing black.