Skip to content
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

Wont run on latest windows insider build (for WSL 2) #1930

Open
identityope opened this issue Jun 15, 2019 · 20 comments
Open

Wont run on latest windows insider build (for WSL 2) #1930

identityope opened this issue Jun 15, 2019 · 20 comments
Labels

Comments

@identityope
Copy link

@identityope identityope commented Jun 15, 2019

I've upgraded to WSL 2 and ConEmu can't be started

image

https://devblogs.microsoft.com/commandline/wsl-2-is-now-available-in-windows-insiders/

Versions

ConEmu build: 190331 x64
OS version: Windows 10 Pro Build 18917

@Maximus5

This comment has been minimized.

Copy link
Owner

@Maximus5 Maximus5 commented Jun 15, 2019

Please report this to wslbridge maintainer. ConEmu just run wslbridge to run wsl.
https://github.com/rprichard/wslbridge

Have you tried to run wsltty itself?

@Maximus5

This comment has been minimized.

Copy link
Owner

@Maximus5 Maximus5 commented Jun 16, 2019

Perhaps you have done something with /mnt prefix and wslbridge fails to run its backend

@identityope

This comment has been minimized.

Copy link
Author

@identityope identityope commented Jun 17, 2019

It seems like wslbridge is broken after this update, related issues here:
rprichard/wslbridge#44
mintty/wsltty#171

@Maximus5

This comment has been minimized.

Copy link
Owner

@Maximus5 Maximus5 commented Jun 17, 2019

The problem is that I'm on slow insider ring and have not received an update yet, so I can't help with fixing

@Maximus5

This comment has been minimized.

Copy link
Owner

@Maximus5 Maximus5 commented Jun 28, 2019

I think I need to force PTY API support and abandon wslbridge

@mxplusb

This comment has been minimized.

Copy link

@mxplusb mxplusb commented Jul 3, 2019

I think I need to force PTY API support

I don't think it should be a problem so long as you version lock it to >1903. I'm on 18922, so I can help test it if you need.

@LostInBrittany

This comment has been minimized.

Copy link

@LostInBrittany LostInBrittany commented Jul 18, 2019

I had the same problem today after installing WSL2, but I've found a nice (and surprisingly simple) workaround: if I change the {Bash:bash} task commands simply to

wsl.exe

it works as intended :)

@tomaspaseka

This comment has been minimized.

Copy link

@tomaspaseka tomaspaseka commented Jul 31, 2019

I had the same problem today after installing WSL2, but I've found a nice (and surprisingly simple) workaround: if I change the {Bash:bash} task commands simply to

wsl.exe

it works as intended :)

I did the same, but arrow keys are not working in vim.

@LostInBrittany

This comment has been minimized.

Copy link

@LostInBrittany LostInBrittany commented Jul 31, 2019

I had the same problem today after installing WSL2, but I've found a nice (and surprisingly simple) workaround: if I change the {Bash:bash} task commands simply to

wsl.exe

it works as intended :)

I did the same, but arrow keys are not working in vim.

I have just tested on my computer, they are working for me

@LesterCovax

This comment has been minimized.

Copy link

@LesterCovax LesterCovax commented Aug 23, 2019

To add to @LostInBrittany 's solution, I'd recommend running wsl ~ instead of just wsl. That way you'll start in your WSL home directory instead of your Windows home directory.

I had a hell of a time trying to figure out how to pass commands through using the -e and -- flags mentioned in the --help entry, as they don't seem to work as I expected (and documentation is limited).

This is my new task definition:

  • chcp 65001 & set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & wsl.exe ~ -- boot.sh -cur_console:t:"Ubuntu"

And this is my old one using the WSL bridge:

  • chcp 65001 & set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & %ConEmuBaseDirShort%\conemu-cyg-64.exe --wsl -cur_console:pm:/mnt -cur_console:t:"Ubuntu" -t boot.sh

I originally had the chcp 65001 in there to make ANSI support work correctly, but I'm not so sure it's necessary anymore. The cur_console portion is to label the tab "Ubuntu". The boot.sh file contains code (cat /<pathToConEmu>/ConEmu/boot.ans) to echo some ANSI sequences (might not be necessary anymore) to initialize the session correctly. echo -e <ANSI escape sequences> can also be used. Then I have an ANSI splashscreen I made displayed via screenfetch.

LesterWslSplash

@inossidabile

This comment has been minimized.

Copy link

@inossidabile inossidabile commented Aug 27, 2019

@LesterCovax nice workaround, thanks. However it's not working too well with Zsh and its magic.

@LesterCovax

This comment has been minimized.

Copy link

@LesterCovax LesterCovax commented Sep 3, 2019

@inossidabile I found out yesterday that it's not working correctly for me either. I was wondering why my color palettes were all screwed up, but it appears if I start the console directly in the account I want, powerline is orange > green > grey like in my previous GIF. If I start the console tab as root in WSL, then su - saitei, it sets it correctly. Not sure if it's a powerline thing or something deeper since all other colors render correctly, and I confirmed the palettes haven't changed.

Incorrect:
image
Correct:
image

@Maximus5

This comment has been minimized.

Copy link
Owner

@Maximus5 Maximus5 commented Sep 4, 2019

@LesterCovax
There may be reason for such behavior.
If your prompt used 256/true-colors than their support are limited to certain areas https://conemu.github.io/en/Xterm256Colors.html#xterm_256_color_mode_requirements
If not - that may be some palette issues or settings.

@LesterCovax

This comment has been minimized.

Copy link

@LesterCovax LesterCovax commented Sep 5, 2019

@Maximus5 it's the same prompt/settings in both scenarios though. The only difference is the entry point...whether I start WSL as root, or directly as my user.

@Biswa96

This comment has been minimized.

Copy link

@Biswa96 Biswa96 commented Sep 14, 2019

@Maximus5 I have made wslbridge2 project. Those works like in-place replacement of old wslbridge, also works in mintty. But I can't run in ConEmu. May you suggest any steps for that?

There are some bugs (static linking) but I shall fix them quickly.

@fpqc

This comment has been minimized.

Copy link

@fpqc fpqc commented Sep 27, 2019

@Biswa96 Maximus would need to recompile his connector against the wslbridge2 project.

@pacanukeha

This comment has been minimized.

Copy link

@pacanukeha pacanukeha commented Oct 16, 2019

I did the same, but arrow keys are not working in vim.

Same for me

@AurelienCordonnier

This comment has been minimized.

Copy link

@AurelienCordonnier AurelienCordonnier commented Dec 17, 2019

In agreement with @LesterCovax, edit the task definition by replacing %ConEmuBaseDirShort%\conemu-cyg-64.exe by wsl.exe in Cmder Settings/Startup/Tasks works fine. Probably that don't realy solve the "wslbridge error" encountered directly, but that gives an answer. I don't know if it is the same result as well...
I have to mention that works also with debian.exe and I think it will be the same for other distributions.

@Prunoideae

This comment has been minimized.

Copy link

@Prunoideae Prunoideae commented Jan 27, 2020

It worked, but with certain bugs messing with GNU-screen and others.

image

The whole console was just messed up when using ctrl-A + | or other things alike to split screens, and also things like vim is not functional as expected.
Also, I tried tmux, upgraded it to version 2.8 and later, but it seemed to be the same as what screen does.

@IPWright83

This comment has been minimized.

Copy link

@IPWright83 IPWright83 commented Feb 10, 2020

@tomaspaseka did you ever get arrow keys working? I've noticed that they start putting garbage to the console :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.