-
Notifications
You must be signed in to change notification settings - Fork 844
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
Executing a symlink to a windows executable does nothing #3999
Comments
I have the same issue in my I have been running A simply repro:
This should get you into cmd but nothing happens after running, and the program doesn't have any output. |
Instead, I now need to write a startup shell script.
Or you may use |
I am able to reproduce with Windows Version WSL + Ubuntu 18.04 LTS Easy repro: Follow https://docksal.io/installation#windows-virtualbox on this setup |
Given we've got multiple simple repros on the most common Ubuntu WSL installation, how can we get the prioritity raised? This is a big one for me... there's only one symlink I have but I use it a lot :-) NO assignees no tags no nothing is a bit sad-face |
The workaround worked for me of creating a file with an exec. Although there's a typo there, you need to start with '/mnt/c/Program Files/' the MNT was missing. |
@bbulkow Not a typo. Most people just change their mount root to |
Same issue on win10 1903 18362.116 with ubuntu 18.04.2 |
This is a problem when the argument is a string with spaces. change to this
|
Working on a fix for this. Will also attempt to get the fix backported to 1903. |
I find that absolute file paths in cmd arguments are also not translated... As a result, I have to add a prefix of |
I've identified the issue, it's related to us now supporting the 9P paths (\wsl$\distro) in wslpath and am drafting a fix. |
I have same issue after upgrade to 1903. I get error what is interesting when i execute symlink as sudo everything works.
|
This is fixed in 18917. |
@benhillis Do you know yet whether a backport to 1903 is possible/likely? I assume it would be delivered through standard Windows Update patching. |
Working great on the insider builds. |
This is still broken in the 1909 update, it used to work in 1809. Frustrating that it just stopped working, and hasn't been fixed for months. Is there any chance a fix can be cherry picked for stable? |
I too am on 1909, and this doesn't work w/ Ubuntu 18.04 WSL. Either the fix has not been published, or it is broken again. |
Unfortunately the Windows servicing team would not take this fix to 1903 / 1909. Fixed in builds 18917 and later. |
As of now, the latest OS build released is 18363.628 (and I'm not daring installing Windows Insider builds) so this feature is broken. Heavily. |
WSL needs /c not //c, and symlinks are fully resolved before calling .exes due to this bug: microsoft/WSL#3999
…kip ci] (#12124) On some versions of Windows, WSL is unable to execute symbolic links to Windows executables (microsoft/WSL#3999). As a workaround for that problem this changes to use resolve() on WSL if win32yank was a symbolic link. fixes #12113.
This still isn't working for me on 2004... |
Hello, the pathology I am seeing is identical to that reported in the following:
#3424
Except it's a year later and clearly a different underlying issue. I have added a report to that issue, but it's closed, so I thought I would open a new issue. I don't know if you'd prefer to proceed in one or the other. This was working for me as recently as a few weeks ago ( say, 3/31/19 ).
I am running 10.0.18362.53
Please fill out the below information:
Your Windows build number: (Type
ver
at a Windows Command Prompt)10.0.18362.53
What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
I have a windows executable installed in program files
cd /usr/local/bin
bin$ sudo ln -s "/mnt/c/Program Files/Sublime Text 3/sublime_text.exe" subl
bin$ ls -l
total 0
lrwxrwxrwx 1 root root 52 Apr 25 12:28 subl -> '/mnt/c/Program Files/Sublime Text 3/sublime_text.exe'
bin$ ./subl
---> this should pop up a windows window, it doesn't
What's wrong / what should be happening instead:
Executing the soft link should execute the windows program.
If I execute the command directly, it works fine
Strace of the failing command,
---> there's an EBADF near the bottom that shows there's a problem instead of a reasonable launch
---> sorry about the bad formatting. Not sure what I'm falling afoul of. Carriage returns and line feeds, I expect.
The text was updated successfully, but these errors were encountered: