Skip to content
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

Arch Linux, Hyprls not starting #10

Open
ARKye03 opened this issue Jun 4, 2024 · 3 comments
Open

Arch Linux, Hyprls not starting #10

ARKye03 opened this issue Jun 4, 2024 · 3 comments

Comments

@ARKye03
Copy link

ARKye03 commented Jun 4, 2024

On VSCode

Version: 1.89.1
Commit: dc96b837cf6bb4af9cd736aa3af08cf8279f7685
Date: 2024-05-07T05:16:23.416Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 6.8.9-zen1-2-zen

$ go version

go version go1.22.3 linux/amd64

At the start, Hyprls returns this in the output:

[Error - 6:27:38 PM] Hypr client: couldn't create connection to server.
Launching server using command hyprls failed. Error: spawn hyprls ENOENT

Trying Hyprls in the terminal:
$ hyprls

2024-06-04T18:29:51.201-0400    DEBUG   hyprls/main.go:25       going to start server
2024-06-04T18:29:51.201-0400    DEBUG   [email protected]/main.go:18        starting server

Does nothing else. HyprLS is installed, and the binaries folder from go is exported to the PATH.
I can use the hyprls command from the terminal, but it won't start.

@ewen-lbh
Copy link
Member

ewen-lbh commented Jun 5, 2024

Hiii! This looks similar to #8, can you try this workaround? #8 (comment)

@ARKye03
Copy link
Author

ARKye03 commented Jun 5, 2024

Hiii! This looks similar to #8, can you try this workaround? #8 (comment)

Thank you, but none of the solutions worked for me, except for the one that invokes VSCode from the terminal; it serves as a workaround for now. Thank you

@baudneo
Copy link

baudneo commented Jun 28, 2024

You modifed the user JSON settings in VSCode and rebooted? I am on Arch as well and had the same issue until I set the proper PATH in the VSCode env and rebooted. Rebooting was key, it didnt work until after a reboot.

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

3 participants