-
-
Notifications
You must be signed in to change notification settings - Fork 575
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
WSL2 no longer working after windows update #2014
Comments
I just ended up bypassing the WSL bridge. Tested on WSL 1 & 2.
The #!/bin/bash
cat /mnt/d/some/long/path/conemu-maximus5/ConEmu/boot.ans
cd ~
screenfetch
bash -l -i |
Thank you. This does indeed work. You don't need to specify the user (the default one, that corresponds to the Windows user, will be used), but you do need to specify the distro (at least in my case, otherwise it doesn't work and exits with "working less than 10 seconds" error). So, essentially, as little as:
is enough. |
Can confirm that the username isn't needed. I think I assumed it was necessary due to me creating a different username for WSL than my Windows account. I suppose it's only necessary if you have multiple user accounts in your WSL distro. The additional Now I just need to figure out how to get rid of the annoying extra entry in the 'Create New Console' dialogue. Been having that issue for years now and have just lived with it . |
You probably haven't named the task so it shows up like that. You can edit all your tasks by opening Settings and going to Startup -> Tasks (yes, it doesn't make too much sense for it to be under Startup, which is probably something for another minor issue report). You can name that task however you want, (the topmost, unlabeled input box) and you can delete any task by selecting it in the list on the left and clicking on the minus (i.e. -) key below the list. |
@bmarkovic The highlighted text there is actually the contents of the |
Lester where do you place bash.sh in order for it to be found when opening a new window? I'd like to do something similar and have tried in in several location but keep getting the error "/bin/bash: bash.sh: command not found" Thanks! |
Can't currently look up my setup but I believe it's in the |
The code in @bmarkovic worked for for me with a minor adjustment: For my install of Ubuntu 20.04, it worked with this: You can get the Linux image name with the following: |
@evoelker thanks, ubuntu doesn't work, Ubuntu with version works. |
I've given up and moved to Windows Terminal, everything works out of the box for my particular setup |
Duplicate: #1930 |
Is it not possible to maintain the benefits of cygwin and work around this bug? |
I believe this bug should be fixed with latest Win 10 21H1 and (possibly) Win 11 release. If anyone was having trouble before updating your OS to latest release should solve your problem. |
Versions
ConEmu build: 191012 [64]
OS version: Windows 10.0.19013.1122 x64
Used shell version: WSL (bash, ubuntu)
Problem description
I've upgraded Windows Insider build today. Since the upgrade, ConEmu WSL task no longer works. It exits with the following error:
This is my
{WSL:Bash}
task command line:Please note that WSL works ok when started as "Ubuntu" in Start Menu, and it works fine with the new Windows Terminal. The only software that has the issue is ConEmu at the moment.
Also, other console types (Git Bash, Windows CMD, Powereshell) all work fine. The only combination that doesn't work is ConEmu with WSL.
I also tried moving the ConEmu.xml to a different location and starting fresh -- to exact same results.
The text was updated successfully, but these errors were encountered: