Unable to use Android Studio's Android Emulator normally under Ubuntu WSL

[linghengqian]

cmd /c ver

Microsoft Windows [版本 10.0.22631.3374]

wsl --status

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

Did the problem occur during installation?

• Yes

What happened?

• Unable to use Android Studio's Android Emulator normally under Ubuntu WSL.
• See the Steps to reproduce Comment section for detailed reproduction steps.

What was expected?

• Normal use of Android Studio's Android Emulator under Ubuntu WSL.

Steps to reproduce

• Execute the following command on the new Ubuntu 22.04 WSL.

sudo apt update && sudo apt upgrade -y

cd /tmp

# The main reason to install `microsoft-edge` is that `jetbrains-toolbox` requires a browser on the system to open the URL.
wget https://packages.microsoft.com/repos/edge/pool/main/m/microsoft-edge-stable/microsoft-edge-stable_122.0.2365.92-1_amd64.deb?brand=M102 -O ./microsoft-edge-stable.deb
sudo apt install --fix-missing ./microsoft-edge-stable.deb -y
# Open `microsoft-edge` and then close it. This is to enable the browser to hook into the URL.
microsoft-edge

sudo apt install libfuse2 libxi6 libxrender1 libxtst6 mesa-utils libfontconfig libgtk-3-bin tar -y
wget https://download-cdn.jetbrains.com/toolbox/jetbrains-toolbox-2.2.3.20090.tar.gz -O ./jetbrains-toolbox.tar.gz
tar -xzf ./jetbrains-toolbox.tar.gz
./jetbrains-toolbox-2.2.3.20090/jetbrains-toolbox --install
rm -rf /tmp/jetbrains-toolbox-2.2.3.20090/

• At this time, open jetbrains-toolbox through ~/.local/share/JetBrains/Toolbox/bin/jetbrains-toolbox. and select Android Studio installation.
• 
• Click OK. Agree to Google's LICENSE and download the SDK.
• 
• 
• 
• Click Finish.
• 
• In the main interface of Android Studio, select Virtual Device Manager through More Actions.
• 
• Click Start to the right of Pixel_3a_API_34_extension_level_7_x86_64.
• 
• 
• After a period of time, the virtual device is not started and no error is reported.
• 
• This seems like a big step forward from How to run Android Studio Emulator via WSL2 microsoft/WSL#6625 , but it's still a big bummer that you can't use virtual devices. I'm not sure where the problem lies.

Additional information

• Null.