Fish Theming can break app launcher.

[mangkoran]

I am using ArchWSL in WSL2. Default shell is fish. Before using gwsl, I tried VcXsrv. I have this in my config.fish : set -x DISPLAY (ip route | awk '/^default/{print $3; exit}'):0.0 and I can launch Linux GUI apps properly (e.g. emacs). When trying gwsl, I can't launch emacs from "Linux Apps" or "Shourcut Creator". But if I manually use "Linux Shell", and then execute emacs, Emacs opened. Here is my logfile: dashboard.log

[mangkoran]

Already tried this, but it still the same (need to manually open apps from Linux terminal). I guess even without this script, it should be fine?

[Pololot64]

I am assuming you have GWSL 1.3.7? This should be fixed in GWSL 1.3.8 but just in case it is not, what language/region is your pc and wsl set to?

[Pololot64]

Also, do you have the store version or github installer version of GWSL?

[mangkoran]

I reported this issue in 1.3.7, then tried the 1.3.8. Both still have the issue. I use GitHub version for both too.

[Pololot64]

And what language again? Sorry. It is an encoding issue

[mangkoran]

I guess this is what you asking? Windows

WSL

[Pololot64]

Thanks. Thinking...

[Pololot64]

Here is a test build that should solve the issue. I did not have time to wrap it in an installer but you can extract it as is and run gwsl.exe. Just testing the app-launcher would be good.

Drive is the fastest way of sharing I can think of. I will remove the link after you get it

[mangkoran]

Downloaded. Going to test it now.

[mangkoran]

Still no luck. I cannot see any logfiles created.

[Pololot64]

Logfiles will still be in appdata/roaming/gwsl

[mangkoran]

Aside from cannot launch emacs from Shortcut Creator, the Linux Apps also displaying loading screen continuously. This is from 1.3.8 and still persist in your recently given build.

[mangkoran]

The only modified logfile is service.log.

[Pololot64]

What version and build of windows 10 do you have?

[Pololot64]

Service.log is unrelated... Wait did you edit your settings.json manually or add a profile?

[mangkoran]

Edition Windows 10 Home Version 20H2 Installed on ‎3/‎23/‎2021 OS build 19042.928 Experience Windows Feature Experience Pack 120.2212.551.0

And no I didn't edit anything.

[Pololot64]

And you have wsl upgraded to at least support wsl2? The machines themselves do not need to be converted to 2

[mangkoran]

Yes my Arch is on WSL2.

Turns out the dashboard.log is modified earlier.

[Pololot64]

That is helpful but these do not mention anything about the new build 5 I sent you... Can you close any previously opened gwsl and run from the new folder again?

[mangkoran]

Still no luck. The dashboard.log is not updated either.

[Pololot64]

Hmm... can you possibly delete the appdata/roaming/GWSL folder completely and then restart the machine?

Technically the error should be fixed so I have no idea what is going on

[mangkoran]

Deleted and restarted, but still cannot launch any Apps.

[Pololot64]

Any new logs now?

[mangkoran]

Only service.log.

[Pololot64]

I know you did not change it but can you post your settings.json file?

[mangkoran]

Renamed it to .txt because GitHub doesn't support JSON settings.json.txt.

[Pololot64]

Oh! I think I know what is going on. Did you allow GWSL through the firewall when it asked?

[Pololot64]

And the app launcher still finds nothing and spins? Did it in 1.3.7? Sorry I think this is a combination of issues some of which are not bugs

[mangkoran]

Yes I allowed all of them. I tried to remove and re-add the entries (pointing to GWSL_instance.exe and GWSL_vcxsrv.exe. And yet still can't launch app.

And the app launcher still finds nothing and spins? Did it in 1.3.7? Sorry I think this is a combination of issues some of which are not bugs

Yes, it spins the whole time. In 1.3.7 it was fine. It showed the list of the apps, but cannot launch them.

[Pololot64]

Hope we are not wasting each other's time with confusion.. This is very bizarre. Especially since dashboard.log is never updated. Can you access the path \\wsl$ in explorer?