| 2019-12-07 07:13:48 |
Jeff Strome |
bug |
|
|
added bug |
| 2019-12-10 13:42:42 |
Balint Reczey |
wslu (Ubuntu): status |
New |
In Progress |
|
| 2019-12-10 13:42:46 |
Balint Reczey |
wslu (Ubuntu): importance |
Undecided |
High |
|
| 2019-12-10 13:43:26 |
Balint Reczey |
bug |
|
|
added subscriber Balint Reczey |
| 2019-12-10 13:45:07 |
Balint Reczey |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-12-10 13:45:07 |
Balint Reczey |
bug task added |
|
wslu (Ubuntu Eoan) |
|
| 2019-12-10 13:45:07 |
Balint Reczey |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-12-10 13:45:07 |
Balint Reczey |
bug task added |
|
wslu (Ubuntu Bionic) |
|
| 2019-12-10 13:45:07 |
Balint Reczey |
nominated for series |
|
Ubuntu Xenial |
|
| 2019-12-10 13:45:07 |
Balint Reczey |
bug task added |
|
wslu (Ubuntu Xenial) |
|
| 2019-12-10 13:45:07 |
Balint Reczey |
nominated for series |
|
Ubuntu Disco |
|
| 2019-12-10 13:45:07 |
Balint Reczey |
bug task added |
|
wslu (Ubuntu Disco) |
|
| 2019-12-10 16:58:36 |
Balint Reczey |
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. |
[Impact]
* Users of Ubuntu on WSL experience long delay in starting the Ubuntu shell when the Windows Firewall is turned on.
[Test Case 1]
* Install Ubuntu in a WSL2 instance
* Enable Windows Firewall for Pubic Network
* (rm -f $HOME/.config/wsl/integration-cache if LP: #1855898 is also fixed)
* run time . /etc/profile.s/wsl-integration.sh
[Test Case 2] ()
(This should be run for (WSL1,WSL2) x (X and PA server running, X and PA server not running) combinations)
* Install Ubuntu in a WSL2/WSL1 instance
* Disable Windows Firewall
* (rm -f $HOME/.config/wsl/integration-cache if LP: #1855898 is also fixed)
* run:
$ unset DISPLAY
$ unset PULSE_SERVER
$ time . /etc/profile.s/wsl-integration.sh
$ echo $DISPLAY $PULSE_SERVER
[Regression Potential]
* The added timeout may be too low for slow/loaded systems making X/PA server auto detection fail. I've picked the timeout value by testing the successful detection attempts in a KVM VM. Pactl commands are consistently slower than xvinfo and WSL1 is consistently slower than WSL2.
[Original Bug Text]
$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. |
|
| 2019-12-10 17:07:04 |
Balint Reczey |
description |
[Impact]
* Users of Ubuntu on WSL experience long delay in starting the Ubuntu shell when the Windows Firewall is turned on.
[Test Case 1]
* Install Ubuntu in a WSL2 instance
* Enable Windows Firewall for Pubic Network
* (rm -f $HOME/.config/wsl/integration-cache if LP: #1855898 is also fixed)
* run time . /etc/profile.s/wsl-integration.sh
[Test Case 2] ()
(This should be run for (WSL1,WSL2) x (X and PA server running, X and PA server not running) combinations)
* Install Ubuntu in a WSL2/WSL1 instance
* Disable Windows Firewall
* (rm -f $HOME/.config/wsl/integration-cache if LP: #1855898 is also fixed)
* run:
$ unset DISPLAY
$ unset PULSE_SERVER
$ time . /etc/profile.s/wsl-integration.sh
$ echo $DISPLAY $PULSE_SERVER
[Regression Potential]
* The added timeout may be too low for slow/loaded systems making X/PA server auto detection fail. I've picked the timeout value by testing the successful detection attempts in a KVM VM. Pactl commands are consistently slower than xvinfo and WSL1 is consistently slower than WSL2.
[Original Bug Text]
$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. |
[Impact]
* Users of Ubuntu on WSL experience long delay in starting the Ubuntu shell when the Windows Firewall is turned on.
[Test Case 1]
* Install Ubuntu in a WSL2 instance
* Enable Windows Firewall for Pubic Network
* (rm -f $HOME/.config/wsl/integration-cache if LP: #1855898 is also fixed)
* run time . /etc/profile.s/wsl-integration.sh
[Test Case 2] ()
(This should be run for (WSL1,WSL2) x (X and PA server running, X and PA server not running) combinations)
* Install Ubuntu in a WSL2/WSL1 instance
* Disable Windows Firewall
* (rm -f $HOME/.config/wsl/integration-cache if LP: #1855898 is also fixed)
* run:
$ unset DISPLAY
$ unset PULSE_SERVER
$ time . /etc/profile.s/wsl-integration.sh
$ echo $DISPLAY $PULSE_SERVER
[Regression Potential]
* The added timeout may be too low for slow/loaded systems making X/PA server auto detection fail. I've picked the timeout value by testing the successful detection attempts in a KVM VM.
Pactl commands are consistently slower than xvinfo and WSL1 is consistently slower than WSL2:
max. | WSL1 | WSL2
----------+-------+------
pactl info| ~0.5s |~0.1s
----------+-------+------
xvinfo | ~0.3s |~0.07s
The CPU used in testing: i5-7300U CPU @ 2.60GHz
[Original Bug Text]
$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. |
|
| 2019-12-10 18:16:37 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~rbalint/ubuntu/+source/wslu/+git/wslu/+merge/376591 |
|
| 2019-12-10 19:44:02 |
Sergey Yukhno |
bug |
|
|
added subscriber Sergey Yukhno |
| 2019-12-10 20:19:19 |
Balint Reczey |
tags |
|
regression-update |
|
| 2019-12-11 15:22:38 |
Robie Basak |
wslu (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2019-12-11 15:22:41 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-12-11 15:22:44 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2019-12-11 15:22:48 |
Robie Basak |
tags |
regression-update |
regression-update verification-needed verification-needed-xenial |
|
| 2019-12-11 15:27:57 |
Robie Basak |
wslu (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2019-12-11 15:28:03 |
Robie Basak |
tags |
regression-update verification-needed verification-needed-xenial |
regression-update verification-needed verification-needed-bionic verification-needed-xenial |
|
| 2019-12-11 15:28:23 |
Robie Basak |
wslu (Ubuntu Disco): status |
New |
Fix Committed |
|
| 2019-12-11 15:28:28 |
Robie Basak |
tags |
regression-update verification-needed verification-needed-bionic verification-needed-xenial |
regression-update verification-needed verification-needed-bionic verification-needed-disco verification-needed-xenial |
|
| 2019-12-11 15:28:47 |
Robie Basak |
wslu (Ubuntu Eoan): status |
New |
Fix Committed |
|
| 2019-12-11 15:28:52 |
Robie Basak |
tags |
regression-update verification-needed verification-needed-bionic verification-needed-disco verification-needed-xenial |
regression-update verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan verification-needed-xenial |
|
| 2019-12-11 17:39:45 |
Launchpad Janitor |
wslu (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2019-12-11 17:39:55 |
Launchpad Janitor |
wslu (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-12-11 17:40:17 |
Launchpad Janitor |
wslu (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-12-11 17:40:25 |
Launchpad Janitor |
wslu (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2019-12-11 19:05:27 |
Launchpad Janitor |
wslu (Ubuntu): status |
In Progress |
Fix Released |
|
| 2019-12-12 16:38:59 |
Łukasz Zemczak |
wslu (Ubuntu Eoan): status |
Fix Released |
Fix Committed |
|
| 2019-12-12 16:40:28 |
Łukasz Zemczak |
wslu (Ubuntu Disco): status |
Fix Released |
Fix Committed |
|
| 2019-12-12 16:42:33 |
Łukasz Zemczak |
wslu (Ubuntu Bionic): status |
Fix Released |
Fix Committed |
|
| 2019-12-12 16:58:27 |
Łukasz Zemczak |
wslu (Ubuntu Xenial): status |
Fix Released |
Fix Committed |
|
| 2019-12-19 13:07:54 |
Balint Reczey |
attachment added |
|
wslu-detection-pa-installed-servers-not-running-wsl2-firewall-on.png https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1855520/+attachment/5314039/+files/wslu-detection-pa-installed-servers-not-running-wsl2-firewall-on.png |
|
| 2019-12-19 13:09:00 |
Balint Reczey |
tags |
regression-update verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan verification-needed-xenial |
regression-update verification-done verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
|
| 2019-12-19 14:14:24 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-12-19 14:14:22 |
Launchpad Janitor |
wslu (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2019-12-19 14:14:43 |
Launchpad Janitor |
wslu (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-12-19 14:28:46 |
Launchpad Janitor |
wslu (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-12-19 14:29:08 |
Launchpad Janitor |
wslu (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2019-12-20 19:47:54 |
Francis Ginther |
tags |
regression-update verification-done verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
id-5def8ed4ce54f7142244d331 regression-update verification-done verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
|
