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.
Screen recording fails on hybrid Intel+NVIDIA systems due to missing VAAPI drivers – should be detected automatically
Reported by PinheiroCosta · filed Oct 22, 2025 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
When trying to use screen recording on a fresh Omarchy installation, the recording failed silently — no video file was saved. After checking the logs, I found the following message:
gsr_get_supported_video_codecs_vaapi: vaInitialize failed
This error means VAAPI wasn’t initialized correctly because the proper driver was missing. And according to assada's comment, the solution depends on the GPU vendor:
For anyone gettinggsr_get_supported_video_codecs_vaapi: vaInitialize failedthis means vaapi isn’t properly set up. AMD:sudo pacman -S libva-mesa-driver mesa-vdpauIntel:sudo pacman -S intel-media-driverNVIDIA:sudo pacman -S libva-nvidia-driver
Originally posted by @assada in [#2628](https://github.com/basecamp/omarchy/issues/2628#issuecomment-3424009321)
My laptop has both an Intel integrated GPU and an NVIDIA GPU.
Even after installing libva-nvidia-driver, the issue persisted — it was only resolved after I also installed the Intel VAAPI driver (intel-media-driver).
So, the root cause seems to be that VAAPI tries to initialize the first available driver (often the wrong one) in hybrid systems. Without both drivers installed, it fails silently.
Expected behavior:
Omarchy (or the underlying recording component) should detect when VAAPI initialization fails and show a clear message explaining the issue.
Ideally, it could suggest which driver to install based on GPU detection (via lspci or similar).
Why this matters:
While not a core bug in Omarchy itself, this issue can affect many users — especially those on laptops with hybrid GPUs — right after a clean install. Improving the detection or error message would greatly improve UX and prevent confusion.
Possible solution
A simple way to improve UX could be to add a small VAAPI check in the screen recording script before starting the recorder:
check_vaapi() {
if ! vainfo >/dev/null 2>&1; then
gpu=$(lspci | grep -E "VGA|3D" | awk -F: '{print $3}' | tr -d ' ')
msg="VAAPI initialization failed. Please install the appropriate driver:\n"
msg+="\nAMD: sudo pacman -S libva-mesa-driver mesa-vdpau"
msg+="\nIntel: sudo pacman -S intel-media-driver"
msg+="\nNVIDIA: sudo pacman -S libva-nvidia-driver"
msg+="\n\nDetected GPU: ${gpu:-unknown}"
notify-send "Screen recording error" "$msg" -u critical -t 10000
exit 1
fi
}
This would prevent the silent failure and guide the user to install the correct driver automatically.
View raw text
When trying to use screen recording on a fresh Omarchy installation, the recording failed silently — no video file was saved. After checking the logs, I found the following message:
`gsr_get_supported_video_codecs_vaapi: vaInitialize failed`
This error means VAAPI wasn’t initialized correctly because the proper driver was missing. And according to assada's comment, the solution depends on the GPU vendor:
> For anyone getting
> `gsr_get_supported_video_codecs_vaapi: vaInitialize failed`
> this means vaapi isn’t properly set up.
>
> AMD: `sudo pacman -S libva-mesa-driver mesa-vdpau`
> Intel: `sudo pacman -S intel-media-driver`
> NVIDIA: `sudo pacman -S libva-nvidia-driver`
_Originally posted by @assada in [#2628](https://github.com/basecamp/omarchy/issues/2628#issuecomment-3424009321)_
My laptop has both an Intel integrated GPU and an NVIDIA GPU.
Even after installing libva-nvidia-driver, the issue persisted — it was only resolved after I also installed the Intel VAAPI driver (intel-media-driver).
So, the root cause seems to be that VAAPI tries to initialize the first available driver (often the wrong one) in hybrid systems. Without both drivers installed, it fails silently.
### Expected behavior:
Omarchy (or the underlying recording component) should detect when VAAPI initialization fails and show a clear message explaining the issue.
Ideally, it could suggest which driver to install based on GPU detection (via `lspci` or similar).
### Why this matters:
While not a core bug in Omarchy itself, this issue can affect many users — especially those on laptops with hybrid GPUs — right after a clean install. Improving the detection or error message would greatly improve UX and prevent confusion.
### Possible solution
A simple way to improve UX could be to add a small VAAPI check in the screen recording script before starting the recorder:
```bash
check_vaapi() {
if ! vainfo >/dev/null 2>&1; then
gpu=$(lspci | grep -E "VGA|3D" | awk -F: '{print $3}' | tr -d ' ')
msg="VAAPI initialization failed. Please install the appropriate driver:\n"
msg+="\nAMD: sudo pacman -S libva-mesa-driver mesa-vdpau"
msg+="\nIntel: sudo pacman -S intel-media-driver"
msg+="\nNVIDIA: sudo pacman -S libva-nvidia-driver"
msg+="\n\nDetected GPU: ${gpu:-unknown}"
notify-send "Screen recording error" "$msg" -u critical -t 10000
exit 1
fi
}
```
This would prevent the silent failure and guide the user to install the correct driver automatically.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.
- Out of scopeDecided by agents · verified · 2026-10-08 23:54 UTC