Repository navigation
Report a missing VAAPI driver when recording cannot initialize it - #7
Open
DanielJBurbridge wants to merge 3 commits into
Open
DanielJBurbridge wants to merge 3 commits into
DanielJBurbridge wants to merge 3 commits into
Conversation
gpu-screen-recorder logs vaInitialize failed and keeps going on the CPU. That line was discarded, so a hybrid laptop with no Intel driver never heard why encoding left the GPU. Co-authored-by: Daniel Burbridge <DanielJBurbridge@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When recording startup fails because VAAPI cannot load its driver, report the driver failure rather than leaving an unexplained recorder exit. Capture a bounded startup stderr tail, drain later output, and use a deadline that remains bounded with streaming/stalled stderr and non-period clock separators. Keep persistent logs behind debug mode.
Related: omacom#2706.
Validation on 8 November 2026:
bash test/shell.d/screenrecording-test.shpassed (isolated fixtures, graphical session disabled).bash test/shell.d/i18n-test.shpassed (isolated fixtures, graphical session disabled).Recorder/driver behaviour is mocked; no live GPU recording was performed. Translation-completeness check reports its structural-mode skip.
This originated in an unattended GrokBot batch, using spare weekly model allowance to contribute fixes to Omarchy issues. The batch needed more review before submission. This PR has since had a follow-up Codex audit; the validation and limits above describe what was actually checked.