[Bug 1855520] Re: Issue with wsl-integration.sh script causing slow start of Ubuntu shell with WSL2

Jeff Strome 1855520 at bugs.launchpad.net
Sat Dec 7 07:22:47 UTC 2019


I should also point out that the IP of 172.24.144.1 was pingable from
the shell.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to wslu in Ubuntu.
https://bugs.launchpad.net/bugs/1855520

Title:
  Issue with wsl-integration.sh script causing slow start of Ubuntu
  shell with WSL2

Status in wslu package in Ubuntu:
  New

Bug description:
  $lsb_release -rd
  Description:    Ubuntu 18.04.3 LTS
  Release:        18.04

  Today I ran an apt update of my WSL2 Ubuntu 18.04.2 LTS installation
  on Windows 10 insider build 19037.1. I then noticed when I launched
  the WSL2 Ubuntu shell that it took about 38 seconds to get a shell
  prompt. This was not an issue until after I did the update. After some
  troubleshooting I found out this delay was because of wsl-
  integration.sh, that the wslu update appears to have added. The
  following two commands:

  env DISPLAY=${WSL_HOST}:0 xvinfo
  env PULSE_SERVER=tcp:${WSL_HOST} pactl info

  in this script are both timing out on my computer. Because both
  commands are timing out, that accounted for the 38 seconds it took to
  get a shell prompt.

  In my case, my WSL_HOST IP was 172.24.144.1 and so I ran these two
  commands:

  env DISPLAY=172.24.144.1:0 xvinfo
  env PULSE_SERVER=tcp:172.24.144.1 pactl info

  and sure enough it took a combined time of about 38 seconds for them
  to timeout. This is only an issue when running Ubuntu in WSL2, not
  WSL1. WSL1 launches fine. In the case of the my WSL1 instance, the
  WSL_HOST appears to be null when running your script, so it assigns
  localhost to WSL_HOST, and both of these commands timeout without
  delay.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1855520/+subscriptions



More information about the foundations-bugs mailing list