wsltty hangs with blank screen

[chrisbouchard]

I updated to Windows 10 Pro version 1809, and since that wsltty has not worked for me. The window opens, but

• the title stays "/bin/wslbridge --distro-guid {a0c91bf4-53b1-4a07-b553-258a8f3de86a} -t -e APPDATA -C ~"
• the window content is blank

I'm using wsltty 1.9.5 with Ubuntu as my WSL distro, from the Windows Store and zsh as my default shell. I'm still able to log into WSL Ubuntu via its standard terminal, and I've noticed that each time I try to open wsltty, new wslbridge-backend and zsh processes are started and stay active even after I close wsltty.

$ ps aux | less

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   8324   140 ?        Ss   14:52   0:00 /init
root         3  0.0  0.0   8332   156 tty1     Ss   14:52   0:00 /init
cboucha+     4  0.0  0.0  19976  5184 tty1     S    14:52   0:01 -zsh
cboucha+    40  0.0  0.0  34724 12828 ?        S    14:52   0:00 /usr/bin/python3 /home/cbouchard/.local/bin/powerline-daemon -q
root        77  0.0  0.0   8332   156 tty2     Ss   14:52   0:00 /init
cboucha+    78  0.0  0.0  37428  1136 tty2     Sl   14:52   0:00 /mnt/c/Users/cbouchard/AppData/Local/wsltty/bin/wslbridge-backend --check-version=0.2.5-dev -356251 -056252 -156253 -kD0136FCB8181438786653570CC6858DD0E9E0B7FF26648AA3B95CD85C1B99EA4 -w8192 -t2048 --pty -c140 -r40 -l -eAPPDATA=C:\Users\cbouchard\AppData\Roaming -eTERM=xterm-256color -C~ --
cboucha+    82  0.0  0.0  19804  4664 pts/0    Ss   14:52   0:00 -zsh
cboucha+   298  0.0  0.0  17380  1916 tty1     R    15:44   0:00 ps aux
cboucha+   299  0.0  0.0  14308  1212 tty1     S    15:44   0:00 less

Open wsltty from Windows and close window...

$ ps aux | less

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   8324   144 ?        Ss   14:52   0:00 /init
root         3  0.0  0.0   8332   156 tty1     Ss   14:52   0:00 /init
cboucha+     4  0.0  0.0  19976  5184 tty1     S    14:52   0:01 -zsh
cboucha+    40  0.0  0.0  34856 12928 ?        S    14:52   0:00 /usr/bin/python3 /home/cbouchard/.local/bin/powerline-daemon -q
root        77  0.0  0.0   8332   156 tty2     Ss   14:52   0:00 /init
cboucha+    78  0.0  0.0  37428  1136 tty2     Sl   14:52   0:00 /mnt/c/Users/cbouchard/AppData/Local/wsltty/bin/wslbridge-backend --check-version=0.2.5-dev -356251 -056252 -156253 -kD0136FCB8181438786653570CC6858DD0E9E0B7FF26648AA3B95CD85C1B99EA4 -w8192 -t2048 --pty -c140 -r40 -l -eAPPDATA=C:\Users\cbouchard\AppData\Roaming -eTERM=xterm-256color -C~ --
cboucha+    82  0.0  0.0  19804  4664 pts/0    Ss   14:52   0:00 -zsh
root       300  0.0  0.0   8332   160 tty3     Ss   15:45   0:00 /init
cboucha+   301  0.1  0.0  37428  1156 tty3     Sl   15:45   0:00 /mnt/c/Users/cbouchard/AppData/Local/wsltty/bin/wslbridge-backend --check-version=0.2.5-dev -356690 -056691 -156692 -k060FA891A775CD39C9EDAAEE09DA9C552B8FF3D106486B18E851D8379D7D91EF -w8192 -t2048 --pty -c140 -r40 -l -eAPPDATA=C:\Users\cbouchard\AppData\Roaming -eTERM=xterm-256color -C~ --
cboucha+   305  3.1  0.0  19804  4704 pts/1    Ss   15:45   0:00 -zsh
cboucha+   372  0.0  0.0  17380  1920 tty1     R    15:45   0:00 ps aux
cboucha+   373  0.0  0.0  14308  1212 tty1     S    15:45   0:00 less

$ ls -l /proc/301/fd
total 0
lrwx------ 1 cbouchard cbouchard 0 Jan 14 15:47 0 -> /dev/tty3
l-wx------ 1 cbouchard cbouchard 0 Jan 14 15:47 1 -> 'pipe:[458]'
l-wx------ 1 cbouchard cbouchard 0 Jan 14 15:45 2 -> 'pipe:[459]'
lrwx------ 1 cbouchard cbouchard 0 Jan 14 15:47 3 -> /unknown
lrwx------ 1 cbouchard cbouchard 0 Jan 14 15:47 4 -> /unknown
lrwx------ 1 cbouchard cbouchard 0 Jan 14 15:47 5 -> /unknown
lrwx------ 1 cbouchard cbouchard 0 Jan 14 15:47 8 -> /dev/ptmx

Only the 0 and 8 links display as valid. The others display as broken links.

I've restarted my entire system, and I've restarted WSL via

> net stop LxssManager
> net start LxssManager

As mentioned earlier, I can run Ubuntu normally from its terminal, and I can run commands from cmd using wsl.

[chrisbouchard]

I'm not sure if this is a wsltty or wslbridge problem. I figured I'd start here because it's more downstream.

[mintty]

I have no clue either, sorry. Works here.
You're starting with the desktop shortcut for the default distro (WSL Terminal)?

[chrisbouchard]

Yes, I've tried it with WSL Terminal, WSL Terminal %, and with a custom shortcut I made.

[chrisbouchard]

And now it's magically working. I'm going to chalk this up to Windows weirdness unless it happens again.