Skip to content

fix: correct aarch64-linux headless shell browser path#17

Draft
pietdevries94 wants to merge 1 commit intopietdevries94:mainfrom
justinmoon:fix-aarch64-headless-shell
Draft

fix: correct aarch64-linux headless shell browser path#17
pietdevries94 wants to merge 1 commit intopietdevries94:mainfrom
justinmoon:fix-aarch64-headless-shell

Conversation

@pietdevries94
Copy link
Owner

The aarch64-linux headless shell browser was incorrectly configured:

  1. mkdir used chromium-headless-shell- (dashes) but makeWrapper used chromium_headless_shell- (underscores) - now both use underscores

  2. makeWrapper used $CHROMIUM_REVISION instead of $CHROMIUM_HEADLESS_SHELL_REVISION - now uses correct variable

  3. Binary was named chrome instead of headless_shell - Playwright expects headless_shell at this path

Without this fix, Playwright fails on aarch64-linux with:
Executable doesn't exist at .../chromium_headless_shell-1200/chrome-linux/headless_shell

The aarch64-linux headless shell browser was incorrectly configured:

1. mkdir used `chromium-headless-shell-` (dashes) but makeWrapper used
   `chromium_headless_shell-` (underscores) - now both use underscores

2. makeWrapper used $CHROMIUM_REVISION instead of
   $CHROMIUM_HEADLESS_SHELL_REVISION - now uses correct variable

3. Binary was named `chrome` instead of `headless_shell` - Playwright
   expects `headless_shell` at this path

Without this fix, Playwright fails on aarch64-linux with:
  Executable doesn't exist at .../chromium_headless_shell-1200/chrome-linux/headless_shell
@pietdevries94
Copy link
Owner Author

@justinmoon Did this actually fix your problem? If so, I would like to upstream it :)

@justinmoon
Copy link

justinmoon commented Dec 22, 2025

Yes it did. I have just been using my fork and it's working very smoothly.

NOTE: I vibe-coded the fix and don't understand it. So buyer beware! This is why I haven't attempted to upstream, yet.

Thanks for making this tool, btw, it has been extremely helpful for me!

@bitbloxhub
Copy link
Collaborator

@justinmoon, does the new main branch after #18 and #21 work for you? Just wondering if I can close this PR.

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.

3 participants