-
Notifications
You must be signed in to change notification settings - Fork 480
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
Path not available in symbolic link #509
Comments
Does this problem happen if you mount with the |
You mean rellinks? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Symbolic links to full path folders produce an error of path unavailable.
How to Reproduce
Create a symbolic link in your home directory pointing to a full path folder, for example
/home/support/lib -> /usr/lib
:From windows, mount the remote root path to Z: using golddrive or sshfs, open Explorer and go to an internal folder of that link, for example :
Z:\home\support\lib\apt
, this works. Then click the lib folder in the address bar, and the error occurs with folder unavailable:Apparently the link target is not resolved correctly, it is resolving
/home/support/usr/lib
and it should be/usr/lib
.Double clicking every folder one at the time in the file browser works ok. The problem is when clicking the link in the address bar.
If the link is pointing to a relative path for example
/home/support/lib2 -> ../../usr/lib
, it works fine, this issue only occurs when the link is pointing to a full path.Environment
The text was updated successfully, but these errors were encountered: