-
Notifications
You must be signed in to change notification settings - Fork 822
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
Fish prompt broken after converting WSL1 instance to WSL2. (link to video included) #4125
Comments
So I had an Ubuntu instance that was already in WSL 2 and was able to install and use the fish prompt as you set it up in your steps in the video. I'll take a look at your logs and see what the error is, some PATH issue seems like the most likely culprit. :) |
@mscraigloewen I just tried it again with an Ubuntu instance already spun up. I set the default to v2, and spun it up. Did the package updates up front. Then I started the fish install. That's where the most recent video starts. |
Looks like #4104 |
@akulbe if you run this command: |
https://1drv.ms/u/s!ApEXGJp7Ipuxi6UkrFBy-GqBIzXwUw Hopefully video is okay, as it gets more than just your answer. I figure as much data as possible might be helpful. |
It might be #4104, or I think it could also a slightly different issue: It seems that the fish shell is trying to access files that are on your PATH that are stored in your 'Program Files (x86)/Common Files/Oracle/Java/javapath' and you don't have access to them. This could be due to them being links, or due to them being non-accessible due to admin rights. I'll install Java and try to repro! |
Yup this is a duplicate of #4104 , it's due to the link in the Java folder. Here's a temporary workaround (though I don't know how stable it will be since I'm sure that java_target folder will often change) We'll track your issue on #4104! Thanks for filing it, I'll close this one out as a duplicate. |
You mentioned the workaround isn't working, please make sure to run the window with administrator privileges and the |
I missed the Thank you, sir! That did the trick. Do you think that "target" directory changes dynamically, or just with each Java revision? |
Couldn't tell you, I'm not sure how Java organizes that folder. So fingers crossed it won't break too often until we get a fix out! |
I had the same problem, but when I try to execute that command I get
|
Okay, so I have the same setup. fish on WSL 2 with Ubuntu and omf → bobthefish, it was all working fine until today when I restarted my computer. I have the same problem when opening terminal but with a lot more entries, even uninstalling Java to remove it from the path leaves me with all the other ones.
I realize this is being tracked in #4104 but since the fix was here I was wondering if there's a temporary fix for this too, hopefully 😶 |
Okay this is weirder than I thought, I opened another tab with Ubuntu and got that same output except at the end there was Then when I opened another tab, now fish is working without an issue and how it normally works. The only thing I did was open bash in cmd and take a look around if it was reading and following symlinks and stuff which was alluded to (it did, and so does fish). I have no clue what changed but at least it's working fine now. |
@aadibajpai |
@aadibajpai @Sicks3c |
Hello, I've the same issue with WSL2 since today:
One lead can be related to the fact that I installed a Python and Ruby environment yesterday For Ruby with Maybe it's the culprits.. |
Strange if I do a |
Ok, I found the problem, after having reinstalled my Ubuntu 20.04 session several times with this problem each time when starting a Fish shell session. Everything is in order if I disable the Fast start-up mode of Win10 ... Hoping to help. |
i use wsl2 and fish-shell too, ever it worked well, studently someday the same issue occurred, after i reboot my pc, it works fine now. That's strange. |
When I install WSL, I set up Fish as my default shell, and then install a couple of plugins.
Once I converted an existing WSL instance to WSL2, that became unusable.
Your Windows build number: (Type
ver
at a Windows Command Prompt)Windows 10 Build 18917.1000
What you're doing and what's happening:
wsl --set-version 2
Open new window of
See video of this happening at https://1drv.ms/v/s!ApEXGJp7Ipuxi6RJIZhqOstDpVV7rg.
NOTE: I edited the video to remove dead air. Some operations seem to have finished much quicker than they actually did. It's still 4 minutes and change.
The text was updated successfully, but these errors were encountered: