Windows 10: Notepad running next to gedit using the initial WSL GUI app support

/u/itsme-alan · Apr 28, 2021

submitted by /u/itsme-alan
[link] [comments]

:)

Tenforo · Apr 28, 2021

Preview of GUI app support available for Windows Subsystem for Linux

A year ago at BUILD 2020 we introduced our goal to bring Linux GUI applications to the Windows Subsystem for Linux (WSL) to run Linux GUI applications. We are proud to announce the first preview of this highly anticipated and open source feature! We’ve given this feature the nickname: “WSLg”. Please check out the video below or keep reading to see what you can use this feature for, how it works, and how to install it.

What can I use GUI application support for?

WSL lets you run a Linux environment, and up until this point has focused on enabling command line tools utilities and applications. GUI app support now lets you use your favorite Linux GUI applications as well. WSL is used in a wide variety of applications, workloads, and use cases, so ultimately, it’s up to you on what you’d like to use GUI app support for. Below, we’ve highlighted some key scenarios to help you fall in love with running applications in a Linux environment.

Use your IDE of choice to develop Linux projects

Visual Studio Code has an amazing experience using VS Code Remote to create a way for you to have a full-fledged Linux IDE directly on your Windows machine, keep extensions and settings across both Windows and different WSL distros (you can view our getting started with VS Code tutorial here. WSLg will let you run other IDEs such as gedit, JetBrains based editors, gvim, etc., to test, build, and debug your Linux applications in a performant manner.

Here’s an example of running gedit and gvim to edit Linux files directly in WSL.

Run Linux only applications, or Linux specific use cases like testing

You can use this feature to run any GUI application that might only exist in Linux, or to run your own applications or testing in a Linux environment. This could be incredibly useful for developers who want to test their cross-platform app, as they can now run it directly on Windows 10, and then easily inside of Linux without ever needing to change machines or manage a virtual machine.

Let’s look at an example of running TestCafe Studio in WSL to do some web testing from a Microsoft Edge browser running in Linux.

Build, test and use Linux applications that use audio or the microphone with built in audio support

Linux GUI applications on WSL will also include out of the box audio and microphone support. This exciting aspect will let your apps play audio cues and utilize the microphone, perfect for building, testing, or using movie players, telecommunication apps, and more.

Here’s an example of using Audacity running on Linux to record some audio and play it back.

Bonus: Leverage WSL’s GPU access to run Linux applications with 3D acceleration

As part of this feature, we have also enabled support for GPU accelerated 3D graphics! Thanks to work that was completed in Mesa 21.0, any applications that are doing complex 3D rendering can leverage OpenGL to accelerate these using the GPU on your Windows 10 machine. This will make some of your more complex applications run smoothly, such as running Gazebo, a robotics simulation tool. This experience will soon be included by default with different WSL distributions, however you can gain access to it right away by following the instructions in this blog post to get the right graphics driver and to ensure your distro has a compatible Mesa version..

Below you can see the Gazebo application simulating a robot exploring a virtual cave, as well as the Rviz application visualizing the camera feed of the robot and its laser field sensor’s output. Thanks to GPU accelerated 3D graphics we can run this demo at 60 FPS!

How does this feature work?

From the demos above, you might have noticed we didn’t need to start an X server manually. That’s because with this feature we are automatically starting a companion system distro, containing a Wayland, X server, pulse audio server, and everything else needed to make Linux GUI apps communicate with Windows. After you’re finished using GUI applications and terminate your WSL distribution the system distro will automatically end its session as well.

Like with the rest of WSL plumbing, our intention is for this component to be fully managed and seamless for users. Our intentions are for this system distro to be as invisible to the user as possible, and this is why you won’t see this system distro when you run wsl -l -v. Lastly, we’re excited to present that we are using Microsoft’s CBL-Mariner distribution for this system distro! CBL-Mariner is an internal Linux distribution used traditionally for Microsoft’s cloud infrastructure and edge products and services, and we are now extending its use to support GUI apps inside of WSL. You can view the diagram below to see an overall summary of the architecture of this feature.

For a full in depth view of what we did to make this feature possible and the deep technical details, please view this blog post written by the developers who made this feature possible.

Getting started with this feature

We are starting the rollout of this feature as an initial preview before we fully roll it into the WSL experience. To get started using Linux GUI app support, you’ll need to make sure you’re on Windows 10 Insiders preview build 21364 or higher. If you already have WSL installed, all you need to do is run wsl --update and you’ll be set to use GUI apps. If you don’t have WSL enabled, running wsl --install will install WSLg automatically as part of the initial WSL setup.

You can find the full install instructions at the GitHub repositories’ README: GitHub - microsoft/wslg: Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios . We also highly recommend that you have GPU compute support enabled in WSL for the best performance, please see this section of the install instructions to see how you can ensure that feature is enabled.

Feedback

Please file any technical issues, or feature requests for GUI application support on the WSLg Github repository. For general WSL issues, please file them at the WSL repository. You can also follow up with me on Twitter @craigaloewen and all WSL team members that are on Twitter using this list. Please stay tuned to this blog for more exciting WSL announcements, and we can’t wait to hear what you think about this new feature.

Craig Loewen
Program Manager, Windows Developer Platform
Click to expand...

Source: https://devblogs.microsoft.com/comma...m-for-linux-2/

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Buddhika Chaturanga · Apr 28, 2021

Launch GUI Application in WSL without XServer

I have installed windows 10 (b.1703) creators update recently and I am using ubuntu subsystem(WSL).There I have installed Visual Studio Code successfully.Problem is that any GUI elements required application cannot be launched(no GUI will be elements displayed reason may be WSL has no direct Graphic driver support).

VSCOE Launch

gEdit Launch

I wanted to know How to provide graphic driver support to WSL in order to facilitate GUI applications? without installing 3rd party software such as XMing-Xserver,putty etc.

Else do we have any other mechanism to achieve it ? only modifying Ubuntu(Linux subsystem) side? other than switching to Windows 10 Insider preview builds?

Bree · Apr 28, 2021

Notepad consuming cpu 40%

Your screenshot of Task Manager and the notepad.exe properties shows the same size and creation date as in @dalchina's earlier screenshot. So it looks like it is the real notepad that's running.

But - it isn't running the way it should. In your Task Manager there should be a > to the left of notepad, and clicking on it should open up a list of the Notepad instances that are running, along with the name of the document that's open (or 'Untitled - Notepad' if none).

Yours doesn't show that (compare it with dalchina's screenshot). Notepad is running - yes, but not the way it's supposed to. It appears to be in the list of background processes, not in the list of Apps where it should be. Could something be trying to run it as a service? Perhaps some malware set this up, but failed to replace the genuine notepad.exe with its counterfeit one?

As a first step I'd look at the Startup tab in Task Manager for clues.

Windows 10: Notepad running next to gedit using the initial WSL GUI app support

Notepad running next to gedit using the initial WSL GUI app support

Notepad running next to gedit using the initial WSL GUI app support

Notepad running next to gedit using the initial WSL GUI app support

Notepad running next to gedit using the initial WSL GUI app support - Similar Threads - Notepad running next

Payful Gedit

Can't run lunix application GUI via WSL 2

Can't run lunix application GUI via WSL 2

Can't run lunix application GUI via WSL 2

Couldn't use wsl gui

Introducing Linux GUI apps running on Windows using the Windows Subsystem for Linux (WSL)

Cannot run GUI app on WSL 2

Running a .exe with no GUI

Run Ubuntu (WSL) app minimized