bash: \wsl$\Ubuntu\home\murkhunting.vscode-server\bin\ea3859d4ba2f3e577a159bc91e3074c5d85c0523/node: cannot execute binary file: Exec format error /usr/bin/bash: Exit 126.
Asked
Active
Viewed 232 times
-1
-
I just got the same (except for the `murkhunting` part of course), including same `ea3859d4...` directory name. This is a regression for me; was working at the end of last week, encountered the error when reran today. Mine is an expo react native project; curious if yours is too @Murkhunting? (could help narrow focus of where the error is) – Daryn Feb 01 '21 at 06:10
-
@Markhunting did you explore others commenting about the same problem? i.e. search hits for `ea3859d4ba2f3e577a159bc91e3074c5d85c0523`? e.g. [here](https://github.com/microsoft/vscode-remote-release/issues/4212), [here](https://github.com/microsoft/vscode-remote-release/issues/4258), [here](https://www.reddit.com/r/vscode/comments/kffqcr/after_upgrading_to_vscode_1521_unable_to_connect/) – Daryn Feb 01 '21 at 06:25
-
I strongly suspect this error is related to others reporting new problems with browser.sh in VSCode 1.52, e.g. https://stackoverflow.com/q/65774451/135114. Note the title of the bash window displaying the error contains the whole bash command being run, which is running the vscode server helper `browser.sh` – Daryn Feb 02 '21 at 06:23
-
@Markhunting you should update your question to give more info if you don't want it to be closed. 1) OS, environment, VSCode version, etc. 2) What you found in searching / tried – Daryn Feb 02 '21 at 06:25
1 Answers
0
Workaround (for people coming here by searching this problem)
run unset BROWSER before running yarn start will solve this problem
Apurv Gupta
- 870
- 7
- 14