cmd /c ver

NA

wsl --status

Also NA in this case, but:

Default Distribution: ntd_Tumbleweed
Default Version: 2

I do have multiple Ubuntu distributions installed, though ;-)

Did the problem occur during installation?

• Yes

What happened?

Visited the Ubuntu WSL Github repo (this repo, of course).

What was expected?

Expect to see a README.md that refers to the Ubuntu WSL project. For instance, ubuntu.exe options, information on contributing to the project, etc.

Steps to reproduce

Visit https://github.com/ubuntu/WSL in a browser. Notice:

• The README.md title is, "WSL Distro Launcher Reference Implementation"
• The README.md is still verbatim the same as that of the reference WSL Distro Launcher project from which this was cloned.
• References launcher.exe instead of ubuntu.exe (and/or its variants)
• Includes email addresses for the Microsoft project
• Includes the build instructions (should probably be a part of a contributing.md) for the launcher.
• Includes the Distro Launcher goals.
• Includes information for uploading to the Microsoft Store.
• Etc.

Additional information

No response

Ubuntu 22.04 LTS app from Microsoft Store fails to install on my Windows 10 PC, even after turning on Developer Mode and enabling Windows Subsystem for Linux feature.

My Windows build is 18362 (2019) running Enterprise edition with full support for Hyper-V.

Tried installing Ubuntu while using PowerShell in admin mode with the command "wsl --install -d ubuntu-22_04", but PowerShell does not understand it. Tried "wsl --install", but yet still flagged the command.

Can anyone help with this please?

On first run of Ubuntu 22.04 the following message is displayed in motd
/etc/update-motd.d/50-landscape-sysinfo: 17: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied

This is not a nice first impression and the package generating this should be removed since landscape is not available on WSL.

cmd /c ver

Win 11 21H2 10.0.22000.708

wsl --status

0.58.3.0

Did the problem occur during installation?

• Yes

What happened?

Language of Windows is French but the slideshow runs in english.

What was expected?

Slideshow should be in french too.

Steps to reproduce

1. Set your system in your local language
2. Start an installation
3. Read the slides, they should be in the same language than the system.

Additional information

No response

Win 11 21H2 / Ubuntu 22.04

Test Case

1. Make sure ubuntu-22.04 is not registered and start the application
2. Wait till the initial installation is done and the dialog "We are almost done" is displayed
3. Click somewhere on the slideshow

Actual result

The dialog disappears and there is no way to proceed (apart from closing the slideshow manually, which results in another error)

Expected result

It must not be possible to close this dialog since it's a modal dialog.

cmd /c ver

Microsoft Windows [Version 10.0.25151.1010]

wsl --status

Default Distribution: docker-desktop
Default Version: 2
WSL version: 0.61.8.0
Kernel version: 5.10.102.1
WSLg version: 1.0.39
MSRDC version: 1.2.3213
Direct3D version: 1.601.0
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.25151.1010

Did the problem occur during installation?

• Yes

What happened?

On Ubuntu 22.04 LTS
After Installing ubuntu on WSL ubuntu , it open WSL ubuntu setup screen but it is completely blank

As you can see in below image

I closed and opened ubuntu 22.04 app and ran this command : sudo LIBGL_ALWAYS_SOFTWARE=1 /usr/libexec/wsl-setup
Now GUI setup screen was visible as you can see below

But after filling details and clicking on setup, it shows setup complete and pc crashes immediately (green screen of death )see below screenshot taken 0.5sec before crash :

Green screen (or blue screen of death)

It says NetAdapterCx.sys failed

After this i tried ubuntu preview (22.10) and faced similar issue : GUI installer failed to launch ,but terminal setup was shown but in terminal it was not taking input (Enter unix name:)
After closing the terminal and launching ubuntu preview app i ran apt update command and again there was green screen of death with same error. NetAdapterCx.sys failed

What was expected?

After Installing ubuntu on Wsl , GUI setup for setting up username and password, etc was expected and after clicking on setup finish installation .
On apt update command it should update list of packages

Steps to reproduce

Install Ubuntu 22.04 from microsoft store
Launch the ubuntu 22.04, after installing ubuntu on wsl screen, it will show blank screen for ubuntu wsl setup
Close ubuntu wsl setup and launch ubuntu app and enter command : sudo LIBGL_ALWAYS_SOFTWARE=1 /usr/libexec/wsl-setup
Finish setup and it will show blue/green screen of death

Install Ubuntu preview from microsoft store
Launch ubuntu preview, after installing ubuntu on wsl screen it will launch terminal saying installer did not completed successfully

and it is not taking any input tried multiple times.
close terminal and launch app, run command apt update it will show green/blue screen of death with error NetAdapterCx.sys failed

Additional information

logs.zip
All logs from /var/logs/installer

cmd /c ver

Microsoft Windows [Version 10.0.22621.819]

wsl --status

Default Distribution: Ubuntu
Default Version: 2

Did the problem occur during installation?

• Yes

What happened?

Just after installing the Ubuntu image and configuring wsl.conf to allow systemd=true on boot, and following the steps here snap version shows snapd as unavailable

What was expected?

snapd should be read as the version 2.57.5+git955.g8ac464e (beta version)

Steps to reproduce

1. Enable systemd support on WSL2 /etc/wsl.conf

[boot]
systemd=true

2. Run these steps

$ sudo apt -y remove snapd --purge # This is the destructive action
$ sudo apt install -y snapd=2.55.3+22.04
$ sudo snap install snapd --beta   # Should install snapd (beta) 2.57.5+git955.g8ac464e
$ sudo snap refresh                # Validation: should not print the same as before
$ sudo apt upgrade snapd          # No need to stay in old version

3. Verify that the version is not shown by

sudo snap version

Additional information

wsl --version

WSL version: 1.0.0.0
Kernel version: 5.15.74.2
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.819

cat /etc/wsl.conf

[boot]
systemd=true

cat %HOMEPATH%\.wslconfig

[wsl2]
memory=2GB

Additional screenshot

There are several missing fonts in the OOBE.
If it's languages we do not support they should be removed.
If we support these languages then the fonts should be added, but then the impact on image size must be estimated.

The following message appears in the console of the slideshow during installation of the distro:
Recovery user information failed with code 80070534

I don't see any subsequent error related to this but it is worrying for a user.

=Test Case=

1. Make sure ubuntu-22.04 is not already registered
2. Run ubuntu-22.04.exe for the first time to start the slideshow
3. Open the console under the slideshow and wait.

==Actual result==
The message "Recovery user information failed with code 80070534" is displayed

==Expected Result==
No error message

Tested on Windows 11 21H2 with Ubuntu 22.04

Graphical installer apparently completes its steps but the console shows error 0x80004004 Operation aborted and applies the fallback method, which fails if the username provided is the same previously provided to the GUI because the installer did create the user in the first place.

wsl --status

Distribuição Padrão: UbuntuDev.WslID.Dev
Versão Padrão: 2
WSL1 não é compatível com a configuração atual da máquina.
 Habilite o componente opcional "Windows Subsystem for Linux" para usar WSL1.

Versão do WSL: 0.58.3.0
Versão do kernel: 5.10.102.1
Versão do WSLg: 1.0.33
Versão do MSRDC: 1.2.2924
Versão do Direct3D: 1.601.0
Versão do Windows: 10.0.22598.200

Windows build number

Windows 11 Dev channel (build 22598)

Test Case

1. Make sure ubuntu-22.04 is not already registered
2. Run ubuntu2204.exe --ui=gui from command line (to ensure GUI mode will be applied).
3. Follow the graphical installation steps. Take a note of the username provided.
4. When allowed click on the "Finish" button.

Actual result

Error message 0x80004004 Operation aborted is displayed, fallback method is applied and it subsequently fails if the same user name is provided because the user was already created by the installer GUI.

Installer did not complete successfully.
Error: 0x80004004 Operation aborted

Applying fallback method.
Please create a default UNIX user account. The username does not need to match your Windows username.
For more information visit: https://aka.ms/wslusers
Enter new UNIX username: carlo
adduser: The user `carlo' already exists.
Enter new UNIX username:

Expected behavior

No error messages and Linux shell opened with the newly created user logged in.

cmd /c ver

Microsoft Windows [Versión 10.0.22623.1028]

wsl --status

Distribución predeterminada: Ubuntu-22.04-test
Versión predeterminada: 2

Did the problem occur during installation?

• Yes

What happened?

LoadCredential breaks systemd-sysusers.service. Currently there is an ugly workaround which writes an override so that no LoadCredential are used:

cat /etc/systemd/system/systemd-sysusers.service.d/override.conf

[Service]
LoadCredential=

Ideally we'd do something more permanent.

What was expected?

systemd-sysusers.service to work with LoadCredential enabled.

Steps to reproduce

Install ubuntu-preview and use:

cat /etc/systemd/system/systemd-sysusers.service.d/override.conf

to see the override. Remove this file and restart WSL. Using systemctl --failed will display systemd-sysusers.service.

Additional information

See this AskUbuntu question for more details:
https://askubuntu.com/questions/1442826/systemd-in-degraded-state-after-enabling-in-wsl

cmd /c ver

Microsoft Windows [Version 10.0.19044.1469]

wsl --status

Default Distribution: Ubuntu
Default Version: 2

Windows Subsystem for Linux was last updated on 2/8/2022
WSL automatic updates are on.

Kernel version: 5.10.60.1

Did the problem occur during installation?

• Yes

What happened?

With Ubuntu 22.04, the installer crashes when the user selects "Help" while changes are being applied.

2022-05-24 07:59:17,277 INFO root:37 start: subiquity/Meta/ssh_info_GET:
2022-05-24 07:59:17,278 INFO root:37 finish: subiquity/Meta/ssh_info_GET: SUCCESS: 500 Traceback (most recent call last):
  File "/snap/ubuntu-desktop-installer/cur...
2022-05-24 07:59:17,278 DEBUG subiquity.server.server:456 request to /meta/ssh_info crashed
Traceback (most recent call last):
  File "/snap/ubuntu-desktop-installer/current/bin/subiquity/subiquity/common/api/server.py", line 122, in handler
    result = await implementation(**args)
  File "/snap/ubuntu-desktop-installer/current/bin/subiquity/subiquity/server/server.py", line 147, in ssh_info_GET
    if self.app.base_model.network:
AttributeError: 'SystemSetupModel' object has no attribute 'network'
2022-05-24 07:59:17,278 ERROR aiohttp.server:355 Error handling request
Traceback (most recent call last):
  File "/snap/ubuntu-desktop-installer/current/usr/lib/python3/dist-packages/aiohttp/web_protocol.py", line 418, in start
    resp = await task
  File "/snap/ubuntu-desktop-installer/current/usr/lib/python3/dist-packages/aiohttp/web_app.py", line 458, in _handle
    resp = await handler(request)
  File "/snap/ubuntu-desktop-installer/current/usr/lib/python3/dist-packages/aiohttp/web_middlewares.py", line 119, in impl
    return await handler(request)
  File "/snap/ubuntu-desktop-installer/current/bin/subiquity/subiquity/server/server.py", line 463, in middleware
    ErrorReportRef, report.ref())
AttributeError: 'NoneType' object has no attribute 'ref'

What was expected?

No crash and the help is displayed.

Steps to reproduce

1. Install Ubuntu 22.04 from the store
2. Proceed with the slideshow, the TUI is displayed
3. Proceed with the installer until the step "Applying changes"
4. Press "Tab" to go to the "Help" button then press "enter"

Additional information

No response

Please describe the question or issue you're facing with "Ubuntu WSL documentation".

*Reported from: https://canonical-ubuntu-wsl.readthedocs-hosted.com/en/latest/

Win 11 21H2 / Ubuntu 22.04

During the initial installation there is a large blank space under the slideshow to display the logs.

On the desktop installation this area shrinks/expands if the console is displayed/hidden.
An alternative would be to add a toggle button to entirely switch between the slideshow and the console, avoiding window resizing.

When having the hosts file generated by WSL, it parses Windows' hosts file and appends some lines of its own:

# This file is automatically generated by WSL based on the Windows hosts file:
# %WINDIR%\System32\drivers\etc\hosts. Modifications to this file will be overwritten.
127.0.0.1	localhost
127.0.1.1	<name of host> 

<Windows hosts file entries>

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

How can I edit those lines that are appended? More specifically, I want to include ::1 localhost which Ubuntu for some reason decided against (although plenty other distros implement it which should be the way to go, e.g. Windows, macOS, Debian, ArchLinux, Gentoo, OpenWrt).

cmd /c ver

Microsoft Windows [Version 10.0.19044.1415]

wsl --status

5.10.102.1

Did the problem occur during installation?

• Yes

What happened?

What was expected?

Steps to reproduce

wsl --install

sudo apt update && sudo apt upgrade -y
sudo apt install zsh -y
sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
git clone --depth=1 https://github.com/romkatv/powerlevel10k.git ${ZSH_CUSTOM:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k
sed -i 's/ZSH_THEME="robbyrussell"/ZSH_THEME="powerlevel10k\/powerlevel10k"/g' ~/.zshrc

Additional information

i want to remove = symbol
can you help me plz?

Please describe the question or issue you're facing with "Ubuntu WSL documentation".

*Reported from: https://canonical-ubuntu-wsl.readthedocs-hosted.com/en/latest/

Win 11 21H2 / Ubuntu 22.04

Currently Windows Terminal is customized with the Ubuntu theme:

but when the command is launched from the start menu, it starts a Windows Console which is not customized.

I'd be nice to apply the Ubuntu theme too.

Description

I had the below two windows updates performed

• Cumulative Update for Windows 11 Insider Preview (10.0.22623.870) (KB5018499)
• Update Stack Package - (Version 1022.1018.1012.0)

And on restart I see a window saying "Something went wrong". And was asked to run the following commands

Something went wrong.
Please restart WSL with the following command and try again:
wsl --shutdown
wsl --unregister DISTRO_NAME

But wsl --unregister DISTRO_NAME is a dangerous command and should not be run by the uninitiated.

--unregister <Distro>
    Unregisters the distribution and deletes the root filesystem.

This does not seem to be a Windows WSL issue. I was redirected to this repo - here is my original issue raised in microsoft/WSL#9049

I've attached the image of the window asking me to run wsl --unregister DISTRO_NAME

Need and use case

No warning is currently given when asking the user to run wsl --unregister DISTRO_NAME .

I had previously faced this same issue ("Something went wrong") and had unknowingly ran wsl --unregister (link to my previous issue - microsoft/WSL#8992 ). Which resulted me in loosing my data, I've recovered since then. But adding a warning to let future users know of the consequence would be great.

Additional information

No response

cmd /c ver

Microsoft Windows [Version 10.0.22000.1098]

wsl --status

Standard-Distribution: Ubuntu-22.04
Standardversion: 2

Did the problem occur during installation?

• Yes

What happened?

When setting a different locale for LC_MESSAGES in /etc/default/locale, it's never applied.

$ locale
LANG=de_DE.UTF-8
LANGUAGE=
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=

What was expected?

The expected outcome would be:

$ locale
LANG=de_DE.UTF-8
LANGUAGE=
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=

This works on my regular Ubuntu hosts, but not in my WSL instances (both 20.04 and 22.04).

Steps to reproduce

$ sudo locale-gen de_DE.UTF-8

$ locale -a
C
C.UTF-8
de_DE.utf8
en_US.utf8
POSIX

$ sudo update-locale LANG=de_DE.UTF-8 LC_MESSAGES=en_US.UTF-8

$ source /etc/default/locale

$ locale
LANG=de_DE.UTF-8
LANGUAGE=
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=

Restarting the whole instance or interchanging UTF-8 and utf8 doesn't affect the outcome.

Additional information

No response

Create a bug report template on github to explain how to report a bug against WSL, the minimum information to provide and the logs to attach.

cmd /c ver

Microsoft Windows [Version 10.0.22621.819]

wsl --status

Default Distribution: Ubuntu-20.04
Default Version: 2

Did the problem occur during installation?

• Yes

What happened?

While coping pasting from the WSL terminal, the WSL suddenly stops and hangs out and finally crashes out.

What was expected?

It should have been copied and pasted easily without crashing.

Steps to reproduce

wsl --version
WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2311

Additional information

No response

cmd /c ver

Microsoft Windows [Version 10.0.22621.1778]

wsl --status

Default Distribution: Ubuntu-22.04
Default Version: 2
WSL1 is not supported with your current machine configuration.
Please enable the "Windows Subsystem for Linux" optional component to use WSL1.

Did the problem occur during installation?

• Yes

What happened?

I have a simple autoinstall yaml file in current directory, containing:

• version
• identity
• packages
• late-commands
• user-data (mainly for write-files)

I ran this command: ubuntu2204.exe install --root --autoinstall .\simple.yaml --ui=none
(I've tried it without --root with same results.)
It's like the whole file is ignored, I don't know where to look for additional logs. I just see the 10 minutes cloud-init wait gap in the logs and that's it.

I don't know if this feature is working, where the docs are for it, what the current limitations are, plans for the future, etc.
It would be nice to be able to preconfigure wsl Ubuntu environment very similar to my VM and barebone installations - obviously I wouldn't touch some stuff like network or storage.

What was expected?

Ubuntu is installed with configuration according to autoinstall yaml file.

Steps to reproduce

I've used this as contents of autoinstall yaml file:

#cloud-config
autoinstall:
  version: 1
  identity:
    realname: whatever
    username: geth
    password: '$1$Dct4aGTo$p1OettH8tlj74w4g5AVN21'
  packages:
    - mc
    - jq
  late-commands:
    - - curtin
      - in-target
      - --
      - sh
      - -c
      - |
        printf 'TODO late-commands\n' >> /var/tmp/testy
  user-data:
    package_update: true
    package_upgrade: true
    ssh_publish_hostkeys: { enabled: false }
    write_files:
      - path: /etc/skel/.vimrc
        content: |
          let &t_SI .= "\<Esc>[?2004h"
          let &t_EI .= "\<Esc>[?2004l"
          inoremap <special> <expr> <Esc>[200~ XTermPasteBegin()
          
          function! XTermPasteBegin()
            set pastetoggle=<Esc>[201~
            set paste
            return ""
          endfunction

Additional information

subiquity-server-debug.log

cmd /c ver

Microsoft Windows [Version 10.0.22000.739]

wsl --status

--- Translation below ---
Distribución predeterminada: Ubuntu
Versión predeterminada: 2

El Subsistema de Windows para Linux se actualizó por última vez el 14/06/2022
El Subsistema de Windows para el kernel de Linux se puede actualizar manualmente con "WSL--Update", pero las actualizaciones automáticas no pueden producirse debido a la configuración del sistema.
Para recibir actualizaciones automáticas del kernel, habilite la configuración de Windows Update: "Recibir actualizaciones para otros productos de Microsoft al actualizar Windows".
Para más información, visite https://aka.ms/wsl2kernel.

Versión de kernel: 5.10.102.1

--- DeepL translation ---
Default distribution: Ubuntu
Default version: 2

The Windows Subsystem for Linux was last updated on 06/14/2022.
The Windows Subsystem for Linux kernel can be updated manually with "WSL--Update", but automatic updates may not occur due to system configuration.
To receive automatic kernel updates, enable the Windows Update setting: "Receive updates for other Microsoft products when updating Windows".
For more information, visit https://aka.ms/wsl2kernel.

Kernel version: 5.10.102.1

Did the problem occur during installation?

• Yes

What happened?

During install, if you go to Help, then About this Installer, you get the following screen:

The error is highlighted here

│  The installer only requires the up and down arrow keys, space (or     │
│  return) and the occasional bit of typing.                             │
│                                                                        │
│  This is version SNAP_VERSION of the installer.
                   ^~~~~~~~~~~~
│                                                                        │
│                             [ Close      ]                             │

What was expected?

It should indicate the version of the installer rather than SNAP_VERSION.

Steps to reproduce

PS> wsl --unregister Ubuntu-22.04 # Or whichever version you prefer
PS> ubuntu2204.exe --ui=tui

Wait for the slideshow to be over and then navigate to Help, then About this Installer.
The errata should show up.

Additional information

No response

cmd /c ver

Microsoft Windows [Version 10.0.22621.755]

wsl --status

Default Distribution: Ubuntu-Preview
Default Version: 2
WSL1 is not supported with your current machine configuration.
Please enable the "Windows Subsystem for Linux" optional component to use WSL1.

Kernel
5.15.68.1-microsoft-standard-WSL2

Did the problem occur during installation?

• Yes

What happened?

Using wsl2 with Ubuntu 22.04 with systemd enable. Try using snap app like firefox or sqlitebrowser or openjdk this error shows:

internal error, please report: running "SNAP NAME" failed: cannot find installed snap "SNAP NAME" at revision XXXX: missing file /snap/SNAP-NAME/XXXX/meta/snap.yaml

What was expected?

That the snap works or open.

• snap list works and shows all snap installed.
• snap refresh works and update all snaps

Steps to reproduce

1. enable systemd support
2. verify snap enable by running snap list
3. snap install firefox
4. snap installed firefox
5. run firefox
6. error message shows

Additional information

Some screenshots for reference.

As you can see, the /snap/openjdk folder is there so the snap is mounted.

But, when try to navigate to the snap meta folder in the WSL2 Ubuntu the command ls -l didn't show any file or folder, but if I open with explorer.exe . I can see all the folders there an the meta folder with the snap.yaml file. This happens with any snap.

I uninstalled and installed multiple times all WSL2 and Ubuntu infrastructure but didn't work.

Thanks for the help.

Win 11 21H2 / Ubuntu 22.04

In the OOBE, in the profile setup stage it must be prohibited to use system users or existing users.
If you do so the OOBE crashes and falls back to text mode:

.

Windows 11 21H2 / Ubuntu 22.04

=Test Case=

1. Open Windows Terminal with 2 tabs
2. With Ubuntu 22.04 installed but not registered run: ubuntu2204.exe

=Expected result=
Setup starts and the terminal window is still available so I can continue working while it's installing

=Actual result=
The terminal windows is hidden and reappears at the end of installation.

Description

• When I enabled the built-in Systemd support for Ubuntu WSL 22.04, I installed a few Snapcraft apps and noticed that the Software app was ready to use. But its version is low, still stuck at 41.5, which is also different from the regular Ubuntu 22.04 software application version.

• 

• 

• When I ran snap refresh --list and sudo apt update & sudo apt upgrade, there were no dependencies to upgrade.

• 

• Software (Ubuntu Store) maybe can get a later version of the update, not stop at 41.5 .

Need and use case

• Software (Ubuntu Store) maybe can get a later version of the update, not stop at 41.5 .
• This should obviously unify Ubuntu WSL with the standard Ubuntu experience.

Additional information

• I'm not quite sure if this is happening because I have Flatpak support installed.
• 

cmd /c ver

Microsoft Windows [Version 10.0.25336.1000]

wsl --status

Distribuição Padrão: Ubuntu-Work
Versão Padrão: 2

Versão do WSL: 1.2.0.0
Versão do kernel: 5.15.90.1
Versão do WSLg: 1.0.51
Versão do MSRDC: 1.2.3770
Versão do Direct3D: 1.608.2-61064218
Versão do DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Versão do Windows: 10.0.25336.1000

Did the problem occur during installation?

• Yes

What happened?

End to end test is failing because subiquity cannot run the check-language-support command, causing the test window to hang or quit too early, causing the test to crash. In a real scenario that is not a hard failure, but it's preventing CI to pass.

What was expected?

End to end test to proceed and quit with success, with locale configured and language packs installed accordingly.

Steps to reproduce

Follow the e2e.yaml workflow, at the time of this writing it consists of:

1. Checkout the repository
2. Unregister and unninstall Ubuntu Preview, if installed/registered
3. .\e2e\pre-e2e-testing.ps1 -AppID UbuntuPreview -RootfsX64 -CertificateThumbprint
4. $env:LAUNCHER_REPO_ROOT=
5. cd e2e/
6. go test .\launchertester\ -timeout 15m -run TestBasicSetup --distro-name Ubuntu-Preview --launcher-name ubuntupreview.exe

Additional information

The relevant piece of the client log:

INFO subiquity_status: WAITING => ApplicationStatus(state: ApplicationState.RUNNING, confirmingTty: , error: null, cloudInitOk: true, interactive: true, echoSyslogId: , logSyslogId: , eventSyslogId: )
INFO subiquity_status: RUNNING => ApplicationStatus(state: ApplicationState.ERROR, confirmingTty: , error: null, cloudInitOk: true, interactive: true, echoSyslogId: , logSyslogId: , eventSyslogId: )
INFO system_shutdown: request reboot (immediate: false)

The relevant part of the server log:

2023-04-13 13:20:15,895 ERROR system_setup.server.controllers.configure:160 Language selector data dir /snap/subiquity/current/usr/share/language-selector seems not to be part of the snap.
2023-04-13 13:20:15,895 DEBUG subiquitycore.utils:96 arun_command called: ['check-language-support', '-d', '/usr/share/language-selector', '-l', 'en_US']
2023-04-13 13:20:15,898 ERROR root:37 finish: subiquity/Configure/configure: FAIL: [Errno 2] No such file or directory: 'check-language-support'
2023-04-13 13:20:15,898 ERROR subiquity.server.server:422 top level error
Traceback (most recent call last):
  File "/snap/subiquity/current/lib/python3.10/site-packages/system_setup/server/controllers/shutdown.py", line 47, in _wait_install
    await self.app.controllers.Install.install_task
FileNotFoundError: [Errno 2] No such file or directory: 'check-language-support'
2023-04-13 13:20:15,900 ERROR subiquity.server.server:422 top level error
Traceback (most recent call last):
  File "/snap/subiquity/current/lib/python3.10/site-packages/system_setup/server/controllers/shutdown.py", line 47, in _wait_install
    await self.app.controllers.Install.install_task
FileNotFoundError: [Errno 2] No such file or directory: 'check-language-support'
2023-04-13 13:20:15,900 INFO root:37 finish: subiquity/Meta/status_GET: SUCCESS: 200 {"state": "ERROR", "confirming_tty": "", "error": null, "cloud_init_ok": true...
2023-04-13 13:20:15,901 INFO aiohttp.access:206 127.0.0.1 [13/Apr/2023:13:20:15 +0000] "GET /meta/status?cur=%22RUNNING%22 HTTP/1.1" 200 353 "-" "Dart/2.19 (dart:io)"
2023-04-13 13:20:15,901 ERROR subiquity.server.server:422 top level error
Traceback (most recent call last):
  File "/snap/subiquity/current/lib/python3.10/site-packages/subiquity/server/server.py", line 406, in _run_error_cmds
    await report._info_task
AttributeError: 'NoneType' object has no attribute '_info_task'

The cause is related to the fact that, since the language-selector-common package is not part of the snap, but seeded. The data directory has been addressed, but the command is not in PATH.

Description

• I recommend adding $HOME/.local/bin to the PATH of a fresh installation of Ubuntu Preview.

Need and use case

• I recommend adding $HOME/.local/bin to the PATH of a fresh installation of Ubuntu Preview.
• In the habits of most Jetbrains users, they install Jetbrains Toolbox within WSL. This results in the following steps.

sudo apt update && sudo apt upgrade -y
sudo apt install gnome-text-editor gimp vlc nautilus x11-apps -y
cd /tmp
sudo apt install libfuse2 libxi6 libxrender1 libxtst6 mesa-utils libfontconfig libgtk-3-bin tar -y
curl -fsSL https://raw.githubusercontent.com/nagygergo/jetbrains-toolbox-install/master/jetbrains-toolbox.sh | bash

• Since $HOME/.local/bin is not in the PATH, the user can either manually add export PATH=$PATH:$HOME/.local/bin in ~/.bashrc, or execute the following command to start Jetbrains Toolbox.

~/.local/bin/jetbrains-toolbox

• $HOME/.local/bin exists by default in the PATH in standard Ubuntu, see https://unix.stackexchange.com/questions/316765/which-distributions-have-home-local-bin-in-path . So why not implement the same behavior in a WSL instance of Ubuntu?

Additional information

Description

When the size of the icon is < 32px the version is unreadable and even the logo is hard to recognize.
When the icon size is < 32px, create versionless square WSL icons.

Need and use case

na

Additional information

No response

=Test Case=

1. In the OOBE go to the page "Profile Setup"
2. Click on the link "https://aka.ms/wslusers"

==Expected Result==
It opens the link in a webbrowser

==Actual Result==
It does nothing.

cmd /c ver

Windows version: 10.0.19045.2311

wsl --status

Default Distribution: Ubuntu-20.04
Default Version: 2

Did the problem occur during installation?

• Yes

What happened?

Systemd atd.service fails to start.
Manual start also fails:

root@VERDE:~# atd -d
Cannot change to /var/spool/cron/atjobs: Permission denied
root@VERDE:~# ls -ld /var/spool/cron/atjobs
drwxrwx--T 2 man disk 4096 Apr 23  2020 /var/spool/cron/atjobs
root@VERDE:~# cd /var/spool/cron/atjobs
root@VERDE:/var/spool/cron/atjobs# ls -la
total 12
drwxrwx--T 2 man  disk 4096 Apr 23  2020 .
drwxr-xr-x 5 root root 4096 Apr 23  2020 ..
-rw------- 1 man  disk    2 Apr 23  2020 .SEQ

What was expected?

atd should start

Steps to reproduce

Verify that WSL is updated:

wsl --version
WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2311

Install Ubuntu 20.04

c:\>wsl --list --online
The following is a list of valid distributions that can be installed.
Install using 'wsl.exe --install <Distro>'.

NAME               FRIENDLY NAME
Ubuntu             Ubuntu
Debian             Debian GNU/Linux
kali-linux         Kali Linux Rolling
SLES-12            SUSE Linux Enterprise Server v12
SLES-15            SUSE Linux Enterprise Server v15
Ubuntu-18.04       Ubuntu 18.04 LTS
Ubuntu-20.04       Ubuntu 20.04 LTS
OracleLinux_8_5    Oracle Linux 8.5
OracleLinux_7_9    Oracle Linux 7.9

c:\>wsl --install Ubuntu-20.04    

Start WSL, enter root shell, edit /etc/wsl.conf and put:

[boot]
systemd=true

Stop WSL wsl --shutdown, confirm that is stopped wsl -l -v, start WSL again, enter root shell:

root@VERDE:~# systemctl status atd
● atd.service - Deferred execution scheduler
     Loaded: loaded (/lib/systemd/system/atd.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2022-12-02 22:33:56 CET; 22min ago
       Docs: man:atd(8)
    Process: 504 ExecStartPre=/usr/bin/find /var/spool/cron/atjobs -type f -name =* -not -newercc /run/systemd -delete (code=exited, status=0/SUCCESS)
    Process: 505 ExecStart=/usr/sbin/atd -f (code=exited, status=1/FAILURE)
   Main PID: 505 (code=exited, status=1/FAILURE)

Dec 02 22:33:56 VERDE systemd[1]: atd.service: Scheduled restart job, restart counter is at 5.
Dec 02 22:33:56 VERDE systemd[1]: Stopped Deferred execution scheduler.
Dec 02 22:33:56 VERDE systemd[1]: atd.service: Start request repeated too quickly.
Dec 02 22:33:56 VERDE systemd[1]: atd.service: Failed with result 'exit-code'.
Dec 02 22:33:56 VERDE systemd[1]: Failed to start Deferred execution scheduler.
root@VERDE:~# atd -d
Cannot change to /var/spool/cron/atjobs: Permission denied

Additional information

I know atd is no longer part of stock Ubuntu install after 20.04.
On Ubuntu 22.04 (same WSL) atd works ok after apt install at.

Windows 21H2 / Ubuntu 22.04

Installing the language packs in WSL takes around 4 min (tested on Azure) while the apt operation is around 30s. It seems that there are networking issues in the WSL instance and downloading takes far more time that it should.
For example, resolving the hostname ends up with a 1s timeout,

This needs investigation.

cmd /c ver

Microsoft Windows [Version 10.0.22621.674]

wsl --status

Default Distribution: AlmaLinux-8
Default Version: 2

Did the problem occur during installation?

• Yes

What happened?

Even when previously able to install microk8s using sudo snap install microk8s --classic it's now suddenly stopped working. This render microk8s stop command unable to execute and emit

Interacting with snapd is not yet supported on Windows Subsystem for Linux.
This command has been left available for documentation purposes only.

messages.

What was expected?

Able to install, start, stop. and uninstall using Snap when systemd is enabled on WSL2.

Steps to reproduce

1. Enable systemd support on WSL2 /etc/wsl.conf

   [boot]
   systemd=true
   

2. Restart using wsl --shutdown
3. Install microk8s
4. Run microk8s start
5. Run microk8s stop (usually works fine, this time it stops working)

Additional information

wsl --version

WSL version: 0.70.0.0
Kernel version: 5.15.68.1
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.674

cat /etc/wsl.conf

[boot]
systemd=true

[automount]
options = ro

Additional screenshot

System
Ubuntu 22.04 from Microsoft store (29 Apr 2022)
Windows 11 21H2, OS build 22000.613
WSL ver. 28/03/2022, Kernel 5.10.102.1

Error message seen on first and subsequent starts:

Failed to retrieve available kernel versions.
Failed to check for processor microcode upgrades.

Possible solution

Discussed at: askubuntu

Short answer:

sudo -e /etc/needrestart/needrestart.conf

Uncomment and change the following settings:

$nrconf{kernelhints} = 0;
$nrconf{ucodehints} = 0;

Comment

• $nrconf{kernelhints} was not seen in my version of needrestart.conf, but solution worked OK
• removing needrestart also works
• the askubuntu discussion suggests solution for WSL1 user may be different.
• Is there need for needrestart to be installed and/or started in WSL version at all.

cmd /c ver

From 10.0.19043 up to 10.0.22610

wsl --status

Unknown, but irrevelent. The app that is crashing is a native Windows app.

Did the problem occur during installation?

• Yes

What happened?

Interpreting the crash reports from the store, it appears that some function part of flutter_windows.dll is accessing an invalid pointer and crashing the slide show.

What was expected?

No crashes, slide show displayed without issues.

Steps to reproduce

Undetermined so far. It's during installation, though.

Additional information

cmd /c ver

Microsoft Windows [Version 10.0.19044.3086]

wsl --status

Default Distribution: Ubuntu-22.04
Default Version: 2

Did the problem occur during installation?

• Yes

What happened?

Unable to run 'Ubuntu Software' (which I believe is snap-store)

What was expected?

Software should run and allow installation of other software

Steps to reproduce

Click 'show applications', click 'Ubuntu Software'

Additional information

I've looked online for people having this issue. I've removed/re-installed snap-store, cleared the appropriate cache, etc.

Description

• Make Ubuntu WSL open Systemd by default.

Need and use case

• According to https://ubuntu.com/blog/ubuntu-wsl-enable-systemd ,the Ubuntu (Preview) on the Microsoft Store has enabled system by default. However, for Ubuntu, users need to start a new WSL instance every time, append fields through sudo vi /etc/wsl.conf, and execute wsl --shutdown in Powershell 7.
• I think the importance of systemd is enough to make it a default option faster.

Additional information

• Null.

Description

As we know gedit command is used to open a file in a new terminal and by which we can write/edit things on it but in WSL, this command is already in ubuntu for desktops but missing in WSL.

Need and use case

• gedit command is available in ubuntu for desktops but not in WSL.
• Helpful for beginners who are learning Linux.
• Don't have to install it manually.

Additional information

No response

cmd /c ver

Microsoft Windows [Version 10.0.22621.457]

wsl --status

Default Distribution: Ubuntu
Default Version: 2
WSL1 is not supported with your current machine configuration.
Please enable the "Windows Subsystem for Linux" optional component to use WSL1.
WSL version: 0.66.2.0
Kernel version: 5.15.57.1
WSLg version: 1.0.42
MSRDC version: 1.2.3401
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.457

Did the problem occur during installation?

• Yes

What happened?

• Setup completes decompressing image.

• Setup spits out a bunch of errors [invisible to the end user if they don't click to show the console log]
  I wasn't able to capture the full output of the errors because the setup utility doesn't seem to allow copying the output, this screencap is the best I could do -
  

• Setup prompts you to continues as if nothing has failed

• User creation step hangs/doesn't complete/spins its wheels indefinitely

What was expected?

• Setup utility decompresses image
• Setup proceeds to user creation window
• Everything's good and working

Steps to reproduce

• Install WSL from store.
• Install 'Ubuntu' from store.
• 'Open' Ubuntu to run graphical setup.
  [click to show console output]

Additional information

If you exit/close at the user creation step before creating the user it seems to fallback to the old cli user creation method which works fine as far as I can see.

The older 'Ubuntu on Windows' and its CLI install/setup, that is used when you run wsl --install ubuntu, appears to work just fine [albeit gives you the older 20.04 LTS]

Please describe the question or issue you're facing with "Ubuntu WSL documentation".

*Reported from: https://canonical-ubuntu-wsl.readthedocs-hosted.com/en/latest/

When the user completes the OOBE, there is a long delay during which additional language packs are being installed.
Moreover, it's completely silent and a user doesn't understand what is going on. We could even imagine the installation is broken.

There should be an option to disable the installation of additional package and just mark them for installation next time updates are applied on the machine. A mechanism similar to language selector on Ubuntu Desktop.
This option should be checked by default with a message that it'll take time to install on first run.

cmd /c ver

Microsoft Windows [Version 10.0.22610.1]

wsl --status

Distribuição Padrão: UbuntuWork
Versão Padrão: 2
WSL1 não é compatível com a configuração atual da máquina.
Habilite o componente opcional "Windows Subsystem for Linux" para usar WSL1.

Versão do WSL: 0.58.3.0
Versão do kernel: 5.10.102.1
Versão do WSLg: 1.0.33
Versão do MSRDC: 1.2.2924
Versão do Direct3D: 1.601.0
Versão do Windows: 10.0.22610.1

Did the problem occur during installation?

• Yes

What happened?

Installation proceeded as expected until last screen. Then, clicking to finish doesn't do anything and no crash or any other sort of output information is displayed.

What was expected?

Installation window close and the shell displays.

Steps to reproduce

Make sure Ubuntu-Preview is not registered.

1. Install the latest UbuntuPreview side load package from GitHub
2. From a terminal or command prompt execute the installation in GUI mode (ubuntu-preview.exe --ui=gui)
3. Follow the installation until the end.
4. Try to click on "Finish" button on the last screen (or any method to close the window).
5. Window will never close.

Additional information

Tested with latest UbuntuPreview from GitHub.
Subiquity logs show the installation completed successfully. No stderr or stdout from the server.
Killing the GUI process from Linux side allows the installation to complete and the shell is presented with the recently created user.
Client log shows that clicking on the Finish button attempts to submit shutdown requests to Subiquity. The server is already finished, but no exception is raised on the GUI side.

ubuntu_wsl_setup.log.txt
.

cmd /c ver

Microsoft Windows [Version 10.0.19045.3570]

wsl --status

默认分发: Ubuntu-20.04
默认版本: 2

Did the problem occur during installation?

• Yes

What happened?

run wsl -d Ubuntu-20.04 after the first WSL bash, error happened.

> wsl -d Ubuntu-20.04

When create WSL2

>wsl
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: CreateProcessParseCommon:708: Failed to translate C:\Users\Frank
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Python311\Scripts\
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Python311\
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Program Files\Common Files\Oracle\Java\javapath
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Program Files (x86)\Common Files\Oracle\Java\javapath
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\WINDOWS
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\WINDOWS\system32
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\WINDOWS\System32\OpenSSH\
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\ProgramData\chocolatey\bin
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\WINDOWS\System32\Wbem
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\WINDOWS\System32\WindowsPowerShell\v1.0\
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Program Files\Git\cmd
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Program Files\Git\mingw64\bin
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate c:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate c:\Program Files\Intel\Intel(R) Management Engine Components\DAL
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Program Files\MiKTeX\miktex\bin\x64\
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Program Files\dotnet\
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Program Files\Docker\Docker\resources\bin
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\ProgramData\DockerDesktop\version-bin
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\WINDOWS\System32\Wbem
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Users\Frank Long\AppData\Local\Programs\Python\Launcher\
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Users\Frank Long\AppData\Local\Programs\Microsoft VS Code\bin
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\Program Files\Azure Data Studio\bin
<3>WSL (975) ERROR: No such file or directory @D:/a/1/s/src/linux/mountutil\mountutilcpp.h:17 (MountEnum)
<3>WSL (975) ERROR: UtilTranslatePathList:2853: Failed to translate C:\WINDOWS\System32\Wbem
distrod 0.1.7

USAGE:
    -bash [OPTIONS] <SUBCOMMAND>

FLAGS:
    -h, --help       Prints help information
    -V, --version    Prints version information

OPTIONS:
    -l, --log-level <log-level>    Log level in the env_logger format. Simple levels: trace, debug, info(default), warn,
                                   error

SUBCOMMANDS:
    create
    disable
    enable
    exec
    help       Prints this message or the help of the given subcommand(s)
    start
    stop

What was expected?

Can run multiple Ubuntu WSL windows in Windows Terminal as before

Steps to reproduce

1. Reboot Windows
2. Start cmd
3. Run "wsl -d Ubuntu-20.04"
4. WSL runs ok
5. Enter "exit" to exit wsl bash
6. Run "wsl -d Ubuntu-20.04" again
7. Error happens

Additional information

1. The Ubuntu distribution worked normally before.
2. Other WSL2 distribution worked.

cmd /c ver

Microsoft Windows [版本 10.0.22621.755]

wsl --status

默认分发: Ubuntu
默认版本: 2

Did the problem occur during installation?

• Yes

What happened?

• The installer lacks a GUI when installing Ubuntu through the Microsoft Store. It looks like https://www.microsoft.com/store/productId/9PDXGNCFSCZV updated something unreasonable.
• 

What was expected?

• There should be a GUI installer similar to Ubuntu (Preview). And Ubuntu (Preview) is normal. Refer to https://www.microsoft.com/store/productId/9P7BDVKVNXZ6 .
• 

Steps to reproduce

• Download and open https://www.microsoft.com/store/productId/9PDXGNCFSCZV .

Additional information

• Null.

cmd /c ver

Microsoft Windows [Versión 10.0.22000.739]

wsl --status

---- Translation below ----

Distribución predeterminada: Ubuntu-20.04
Versión predeterminada: 2

El Subsistema de Windows para Linux se actualizó por última vez el 14/06/2022
El Subsistema de Windows para el kernel de Linux se puede actualizar manualmente con "WSL--Update", pero las actualizaciones automáticas no pueden producirse debido a la configuración del sistema.
Para recibir actualizaciones automáticas del kernel, habilite la configuración de Windows Update: "Recibir actualizaciones para otros productos de Microsoft al actualizar Windows".
Para más información, visite https://aka.ms/wsl2kernel.

Versión de kernel: 5.10.102.1

---- DeepL Translation ----

Default distribution: Ubuntu-20.04
Default version: 2

The Windows Subsystem for Linux was last updated on 06/14/2022.
The Windows Subsystem for Linux kernel can be updated manually with "WSL--Update", but automatic updates may not occur due to system configuration.
To receive automatic kernel updates, enable the Windows Update setting: "Receive updates for other Microsoft products when updating Windows".
For more information, visit https://aka.ms/wsl2kernel.

Kernel version: 5.10.102.1

Did the problem occur during installation?

• Yes

What happened?

Graphical bug during install:

Running Ubuntu WSL on Windows 11.

Ubuntu 22.04 LTS freshly downloaded from Microsoft Store.
Unregistering and running again does not fix the error.

Cannot progress, as the Continue or Accept button is hidden by the graphical bug (I presume).
If I press x, Ubuntu WSL works fine but I enter as root.

The bug is purely visual, I can still click over the buggy half and the language under it is selected.

I could only bypass it via:
wsl ubuntu2204.exe --gui=none

What was expected?

No graphical bug, all the screen should be visible.

Steps to reproduce

1. Install Ubuntu 22.04 LTS from the Windows Store
2. Start Ubuntu 22.04 LTS. Bug shows up here
3. wsl --unregister Ubuntu20.04
4. Start Ubuntu 22.04 LTS. Bug shows up here again
5. Goto 3

Alternatively, create an empty flutter app and run it, it will also break:

Additional information

I also managed to reproduce this issue in 20.04 LTS, with the flutter app.
Not all apps with a GUI are broken, QTCreator and xclock both work fine in Ubuntu 20.04 and Ubuntu 22.04.

No response

cmd /c ver

Microsoft Windows [Version 10.0.19045.2673]

wsl --status

Default Distribution: Ubuntu-22.04
Default Version: 1

Did the problem occur during installation?

• Yes

What happened?

When I'm online (connected to the internet) and I turn on vscode in WSL, it opens well. But the minute I'm offline and open vscode in wsl, it does not open the folder/files I'm working on. When I try starting vscode when offline, it displays the following:

"The editor could not be opened due to an unexpected error: ENOPRO: Np file system provider found for resource 'vscode-remote://wsl%2Bubuntu-22.04/mnt/c/...path/to/file'

When I check the log, it shows many lines of error, notable among them is:

[2023-03-08 13:01:06.864] Error: Unable to retrieve mac address (unexpected format)
[2023-03-08 13:01:06.864]
[2023-03-08 13:01:06.864] Error: Unable to retrieve mac address (unexpected format)
[2023-03-08 13:01:06.864] at S (/home/okesiri/.vscode-server/bin/92da9481c0904c6adfe372c12da3b7748d74bdcb/out/vs/server/node/server.main.js:63:3251)
[2023-03-08 13:01:06.864] at v (/home/okesiri/.vscode-server/bin/92da9481c0904c6adfe372c12da3b7748d74bdcb/out/vs/server/node/server.main.js:74:8276)
[2023-03-08 13:01:06.864] at async /home/okesiri/.vscode-server/bin/92da9481c0904c6adfe372c12da3b7748d74bdcb/out/vs/server/node/server.main.js:74:8133
[2023-03-08 13:01:06.864] at Timeout._onTimeout (/home/okesiri/.vscode-server/bin/92da9481c0904c6adfe372c12da3b7748d74bdcb/out/vs/server/node/server.main.js:8:12)
[2023-03-08 13:01:06.864] at listOnTimeout (node:internal/timers:559:17)
[2023-03-08 13:01:06.864] at processTimers (node:internal/timers:502:7)
[2023-03-08 13:01:06.864] VS Code Server for WSL closed unexpectedly.
[2023-03-08 13:01:07.063] Download in background is enabled
[2023-03-08 13:01:08.945] WSL Daemon exited with code 0

What was expected?

It is meant to open as it always has.

Steps to reproduce

To reproduce error,

1. Turn of internet connection
2. Start VSCode.

Additional information

[2023-03-08 13:01:06.864] Error: Unable to retrieve mac address (unexpected format)
[2023-03-08 13:01:06.864]
[2023-03-08 13:01:06.864] Error: Unable to retrieve mac address (unexpected format)
[2023-03-08 13:01:06.864] at S (/home/okesiri/.vscode-server/bin/92da9481c0904c6adfe372c12da3b7748d74bdcb/out/vs/server/node/server.main.js:63:3251)
[2023-03-08 13:01:06.864] at v (/home/okesiri/.vscode-server/bin/92da9481c0904c6adfe372c12da3b7748d74bdcb/out/vs/server/node/server.main.js:74:8276)
[2023-03-08 13:01:06.864] at async /home/okesiri/.vscode-server/bin/92da9481c0904c6adfe372c12da3b7748d74bdcb/out/vs/server/node/server.main.js:74:8133
[2023-03-08 13:01:06.864] at Timeout._onTimeout (/home/okesiri/.vscode-server/bin/92da9481c0904c6adfe372c12da3b7748d74bdcb/out/vs/server/node/server.main.js:8:12)
[2023-03-08 13:01:06.864] at listOnTimeout (node:internal/timers:559:17)
[2023-03-08 13:01:06.864] at processTimers (node:internal/timers:502:7)
[2023-03-08 13:01:06.864] VS Code Server for WSL closed unexpectedly.
[2023-03-08 13:01:07.063] Download in background is enabled
[2023-03-08 13:01:08.945] WSL Daemon exited with code 0

cmd /c ver

Microsoft Windows [Versión 10.0.22623.1028]

wsl --status

Distribución predeterminada: Ubuntu-22.04-test
Versión predeterminada: 2

Did the problem occur during installation?

• Yes

What happened?

systemd-binfmt.service remounts the /proc/sys/fs/binfmt_misc/ directory, where WSLInterop is located and now overriden.

This directrory is shared across distros meaning that any distro can break all others' interop.

What was expected?

Interop should not be broken by a service, much less across distros.

Steps to reproduce

0. wsl --shutdown
1. Start any WSL distro that does not have systemd enabled.
2. Assert that /proc/sys/fs/binfmt_misc/WSLInterop exists.
3. Enable systemd and exit
4. wsl --shutdown
5. Start the distro
6. See that /proc/sys/fs/binfmt_misc/ no longer contains WSLInterop.
7. See that notepad.exe fails.

Additional information

No response

cmd /c ver

Microsoft Windows [Version 10.0.22621.521]

wsl --status

Default Version: 2
WSL1 is not supported with your current machine configuration.
Please enable the "Windows Subsystem for Linux" optional component to use WSL1.
WSL version: 0.66.2.0
Kernel version: 5.15.57.1
WSLg version: 1.0.42
MSRDC version: 1.2.3401
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.521

Did the problem occur during installation?

• Yes

What happened?

There is a screen asking to setup username and password:

When I click continue, nothing happens, and installation is left incomplete, with root user as default

What was expected?

it should work

Steps to reproduce

Install Ubuntu 22.04 from Microsoft Store and follow installation steps

Additional information

No response