It is not a bug in GWSL but a side effect of the complexity of Wsl networking. It breaks a lot. For gwsl I picked the display export method that works for most people. Every now and then, however, it does not work because there are too many unknowns.

It is not a bug in GWSL but a side effect of the complexity of Wsl networking. It breaks a lot.

I understand and I appreciate what's been done already. It's amazing to be able to do this at all imho. I did some digging before posting my issue here and found several discussions that was in the same ball park as this. Since I did feel this case differed a little, I took the time to write it down anyway.

The basic concept is not hard to understand: A host machine (my Windows 10 rig) runs a virtual Linux machine, using hardware supported virtualization and Windows Subsystem for Linux. I assume the vEthernet adapter is the virtual network address for this virtual machine.

Let me try to formulate a question, or two to be precise: Is the issue here that the GWSL generated lines in .bashrc will get different kinds of ip for different combinations of distros and virtualization setups? Or is it that GWSL actually get the intended ip with the generated lines, but that for some people the WSL ip works and for others the physical ip?

If it is the former case I am quite happy with your explanation and how things are. I'm totally fine with having to adapt my Linux environment to export the apropriate DISPLAY variable. Perhaps it's possible to enhance documentation somewhere explaining what the DISPLAY variable should reflect in order to get it to work (as a complement to "just" automate the export of it). Or maybe I din't RTFM properly. Quite possible, if not likely.

On the other hand: if - for some reason - some people get GWSL to work using the physical ip of the host and others using the virtual ip, then I'm totally lost. Even if it's complicated under the hood, it does not make sense to me. I guess I have to dig deeper if this is the case and I want to know more.

In the end, I seem to have found a way (allthough manually only for now) to get things going so I'm quite happy with that. Thank you for your kind reply and all the effort made to make this amazing piece of software.

I believe it is this "Or is it that GWSL actually get the intended ip with the generated lines, but that for some people the WSL ip works and for others the physical ip?" but I could be wrong. In some cases people have reported that it points to the dns when changed.

I would add something to the manual but I do not actually know another all encompassing alternative for the "non-standard" setups so I have not done that for that reason. If you can post your method I can add it with a note. :)