Skip to content

Searching does not work with EACCES error #1666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jpmsilva opened this issue May 18, 2020 · 4 comments
Closed

Searching does not work with EACCES error #1666

jpmsilva opened this issue May 18, 2020 · 4 comments
Milestone

Comments

@jpmsilva
Copy link

Reproduced with docker installation in version 3.3.0.
When trying to search (Ctrl+Shift+F) an error appears:

spawn /usr/lib/code-server/lib/vscode/node_modules/vscode-ripgrep/bin/rg EACCES

Looking inside the container I see that the binary under the path mentioned does not have execute permissions:

root@708059e3622c:~# ls -la /usr/lib/code-server/lib/vscode/node_modules/vscode-ripgrep/bin/rg
-rw-r--r-- 1 root root 5037104 May 17 23:01 /usr/lib/code-server/lib/vscode/node_modules/vscode-ripgrep/bin/rg

Granting the necessary execute permissions fixes the issue:
chmod +x /usr/lib/code-server/lib/vscode/node_modules/vscode-ripgrep/bin/rg

@penuts7644
Copy link

penuts7644 commented May 18, 2020

Can confirm, having the same issue using the NPM installed version of code-server. This also breaks certain extensions like Todo Tree...

For the NPM install the directory is slightly different: /usr/lib/node_modules/code-server/lib/vscode/node_modules/vscode-ripgrep/bin/rg

@kylecarbs
Copy link
Member

Fixing now, sorry about this!

@nhooyr nhooyr assigned nhooyr and unassigned nhooyr May 18, 2020
@nhooyr
Copy link
Contributor

nhooyr commented May 18, 2020

Duplicate of #1665

@nhooyr nhooyr marked this as a duplicate of #1665 May 18, 2020
@nhooyr nhooyr closed this as completed May 18, 2020
@nhooyr nhooyr added this to the v3.3.1 milestone May 18, 2020
@jpmsilva
Copy link
Author

Hi, sorry for the duplicate.
I can confirm that using 3.3.1 the issue is fixed.
Thanks for the very fast response!

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

No branches or pull requests

4 participants