-
Notifications
You must be signed in to change notification settings - Fork 405
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
Error: Can't create the symlink for multishells #938
Comments
the same |
After installing
The error happens on the execution of
which was added to my Also, neither
As workaround I changed the owner of that directory with:
System info: $ lsb_release -d
Description: Ubuntu 22.04.3 LTS |
I am also getting this error, though I am trying to run Perhaps fnm could try creating this directory, with the proper ownership and permissions, before trying to write to it? Not sure if that is a feasible option or not. Thanks! |
Also running into this issue, exact same setup as @jnunderwood. Worked just fine yesterday, booted up this morning after a Windows update and got the error. |
I believe I found a solution. Just set the environment variable export XDG_RUNTIME_DIR="$HOME/.cache/xdgr" Now |
I added this line to my error: Can't create the symlink for multishells at "/run/user/1000/fnm_multishells/7064_1708262245393". Maybe there are some issues with permissions for the directory? No such file or directory (os error 2) Since the directory My previous workaround doesn't work anymore, when I run: sudo chown -R $(whoami) /run/user/1000/ now I get the error: chown: cannot access '/run/user/1000/': No such file or directory After I create the directory with: sudo mkdir /run/user/1000 then I am able to apply the workaround with This works only temporarily, after some time for some reason the directory |
Hi @lackovic. I was experiencing the same situation, until I made my change (above). The only thing I can think of is that the # fnm - fast node manager
export XDG_RUNTIME_DIR="$HOME/.cache/xdgr"
eval "$(fnm env --use-on-cd)" Hopefully that helps. |
CENTOS 7
just installed
fnm
using:then running command:
also errors when runnng command
fnm env
The text was updated successfully, but these errors were encountered: