[fix] Enable accelerated Alacritty with corrected VirGL - #176
Draft
Fail-Safe wants to merge 1 commit into
Draft
Conversation
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.
Remove the factory Alacritty wrapper that forces software rendering once the corrected VirGL runtime is available. This lets normal Alacritty launches use its accelerated GLES renderer instead of requiring users to bypass the wrapper manually.
Blocked on startergo/homebrew-virglrenderer#3 and a published, validated package containing that fix. Do not merge this draft as-is: the current dependency pin is unchanged, and removing the wrapper with that runtime can restore the blank-window bug.
Included in this draft
/usr/local/bin/alacrittysoftware-rendering wrapper and its installation permission entry.Required before ready for review/merge
Evidence and limits
The equivalent driver fix was tested with Try Omarchy's pinned driver source. The unpatched accelerated calibration was blank; the patched runtime rendered correctly and passed targeted pixel checks. A controlled benchmark with identical guest contents and display geometry measured about 32% lower Alacritty/workload guest process CPU versus software rendering (three trials per working condition), with essentially unchanged overall elapsed time. This is not a general speedup, FPS, or battery-life claim.
The patched pinned runtime also passed terminal fullscreen/resizing, scrollback, workspace return, reopen, and bidirectional text clipboard checks. Those experimental-runtime results do not replace validation of the eventual published package and this final integration.
Kitty's separate OpenGL compatibility workaround remains outside this change. The separately reproduced pre-existing combined MRT transition failure is not fixed here.
Draft branch validation
Full
make testpasses with the installed Xcode toolchain, including the updated guest contract. The first run with Command Line Tools could not load the Swift Testing framework; rerunning with Xcode passed. A full final-package build is intentionally pending the real dependency pin above.