An XWayland DE GUI inside WSL Distros' Flavor, e.g., Kubuntu or Debian KDE?

[Adhjie]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I want a GUI DE inside wsl, not just server version of the distros, is it possible to add DE flavors besides wsl --install <distros' names>?

Describe the solution you'd like
A clear and concise description of what you want to happen.

Make the gist in "additional context" section included as official DE flavors of wsl distros --list in wsl --install <distro's name> --DE-flavor parameter maybe?

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

None.

Additional context
Add any other context or screenshots about the feature request here.

1. https://eylenburg.github.io/de_comparison.htm
2. https://gist.github.com/tdcosta100/e28636c216515ca88d1f2e7a2e188912

Installing components

Installing GUI

1. First you select your favorite desktop environment metapackage. Here is a list of the most common metapackages:

   Distro	Desktop Environment	Metapackage
   Ubuntu	Budgie	ubuntu-budgie-desktop (currently very buggy, I don't recommend using it)
   	GNOME	ubuntu-desktop
   	KDE	kubuntu-desktop
   	Kylin	ubuntukylin-desktop
   	LXDE	lubuntu-desktop
   	MATE	ubuntu-mate-desktop
   	Studio	ubuntustudio-desktop
   	Unity	ubuntu-unity-desktop
   	Xfce	xubuntu-desktop
   Ubuntu/Debian	Cinnamon	task-cinnamon-desktop
   	GNOME	task-gnome-desktop
   	GNOME Flashback	task-gnome-flashback-desktop
   	KDE Plasma	task-kde-desktop
   	LXDE	task-lxde-desktop
   	LXQt	task-lxqt-desktop
   	MATE	task-mate-desktop
   	Xfce	task-xfce-desktop

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[Adhjie]

/feature

[github-actions]

Diagnostic information

Found '/feature', adding tag 'feature'