Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Enable VA-API hardware acceleration in default Chromium flags
Reported by Reventlow · filed Feb 27, 2026Closed upstream on 2026-07-18. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Problem
Omarchy's default chromium-flags.conf doesn't include VA-API flags, so hardware video decode/encode falls back to software rendering on Intel GPUs. This causes unnecessary CPU load, high temperatures, and fan noise — especially during video calls (Teams, Meet) and video streaming.
On a ThinkPad X1 Carbon Gen 13 (Lunar Lake), a simple Teams meeting pushes the CPU to 80°C with fans at ~7000 RPM. The Intel iHD driver fully supports VA-API (H264, HEVC, VP9, AV1), but Chromium doesn't use it without explicit flags.
Proposed change
Add these flags to the default chromium-flags.conf:
--enable-features=VaapiVideoDecodeLinuxGL,VaapiVideoEncoder
--enable-gpu-rasterization
--enable-zero-copy
--ignore-gpu-blocklistThis would also benefit the Electron flag files (electron-flags.conf, etc.) since Electron apps like Teams and Spotify have the same issue.
Why it's not enabled by default
Chromium disables hardware acceleration on Linux by default due to driver compatibility concerns across the wide variety of GPU drivers. Since Omarchy targets a known setup (Arch + Intel/AMD), it should be safe to enable by default.
Verification
After adding the flags, hardware acceleration can be verified in Chromium at chrome://gpu — look for "Video Decode: Hardware accelerated" and "Video Encode: Hardware accelerated".
View raw text
## Problem Omarchy's default `chromium-flags.conf` doesn't include VA-API flags, so hardware video decode/encode falls back to software rendering on Intel GPUs. This causes unnecessary CPU load, high temperatures, and fan noise — especially during video calls (Teams, Meet) and video streaming. On a ThinkPad X1 Carbon Gen 13 (Lunar Lake), a simple Teams meeting pushes the CPU to 80°C with fans at ~7000 RPM. The Intel iHD driver fully supports VA-API (H264, HEVC, VP9, AV1), but Chromium doesn't use it without explicit flags. ## Proposed change Add these flags to the default `chromium-flags.conf`: ``` --enable-features=VaapiVideoDecodeLinuxGL,VaapiVideoEncoder --enable-gpu-rasterization --enable-zero-copy --ignore-gpu-blocklist ``` This would also benefit the Electron flag files (`electron-flags.conf`, etc.) since Electron apps like Teams and Spotify have the same issue. ## Why it's not enabled by default Chromium disables hardware acceleration on Linux by default due to driver compatibility concerns across the wide variety of GPU drivers. Since Omarchy targets a known setup (Arch + Intel/AMD), it should be safe to enable by default. ## Verification After adding the flags, hardware acceleration can be verified in Chromium at `chrome://gpu` — look for "Video Decode: Hardware accelerated" and "Video Encode: Hardware accelerated".
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.