

Chrome sadly doesn't for another reason of note. Feel free now to run whatever: Firefox and virt-manager work. Sudo sed -i 's$.*$tcp:host=localhost,port=0$' /etc/dbus-1/nfĪnd now close bash, and open it again. An easy way to do this is to execute the following: In /etc/dbus-1/nf, you need to replace unix:tmpdir=/tmp with tcp:host=localhost,port=0 and then you are done.

Now X programs will show the window correctly.ģ) Now we need to fix dbus: The issue with this was that by default, dbus uses unix sockets to communication, which windows bash at the moment doesn't support. vcxsrv and Xming are confirmed to both work just fine.Īdd DISPLAY=:0.0 to your bashrc: you can do this by executing the following command And surprisingly, it was fairly easy.Īll that needed to be done (From a clean install of windows 10 with Bash installed, of course) was do three steps: virt-manager needs a dbus server to even launch, so I started trying to get it running: And I succeeded. However, the main application I wanted to run for this was virt-manager, because I wanted to be able to administrate qemu servers on windows without having to use a VM to run that. This results in applications like Firefox or virt-manager (when ran in the linux subsystem) to crash either on launch or after a short time, and so it's seen as fairly buggy. So, most people who are using bash subsystem in the windows 10 insider builds seem to be aware that it's possible to use X servers for windows such as vcxsrv or Xming, but most applications require the dbus service, which doesn't work.
