Skip to content

[fix] Enable accelerated Alacritty with corrected VirGL - #176

Draft
Fail-Safe wants to merge 1 commit into
omacom:mainfrom
Fail-Safe:codex/virgl-dual-source-integration
Draft

[fix] Enable accelerated Alacritty with corrected VirGL#176
Fail-Safe wants to merge 1 commit into
omacom:mainfrom
Fail-Safe:codex/virgl-dual-source-integration

Conversation

@Fail-Safe

Copy link
Copy Markdown
Contributor

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

  • Remove the factory /usr/local/bin/alacritty software-rendering wrapper and its installation permission entry.
  • Update the guest contract check to require use of the normal binary without that wrapper.

Required before ready for review/merge

  • Driver PR Keep Hyprland toggle catalog out of new-user state #3 is accepted and a tested patched package is published.
  • Update both runtime dependency-pin scripts with the actual package URL, version, archive layout, and verified SHA256. Verify deployment target and dependency compatibility; do not assume the newer package matches the existing ANGLE/libepoxy pair.
  • Provide safe existing-guest handling: recognize the exact factory wrapper, preserve a backup, and remove the override only after the host runtime is updated. Preserve custom user wrappers; no factory reset should be required.
  • Run the full build and test suite against the final dependency pin, verify the packaged app, and boot a fresh factory guest.
  • Confirm normal terminal selection launches accelerated Alacritty with visible output, expected renderer identity, and passing pixel/state-transition checks. Repeat packaged-app interaction checks.

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 test passes 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant