Any Linux app is not opening about gwsl-source HOT 115 CLOSED

The firewall solution worked for me as well, thanks

from gwsl-source.

Cool. In that case I think I'll close the issue then :)

from gwsl-source.

That's ok. Yep I relate. I tried to make it add the rule automatically but Microsoft did not want that in the store :)

If you want you can allow it through Control Panel --> System and Security --> Allow an app through Windows firewall. Make sure the public boxes of GWSL_vcxsrv.exe and GWSL_instance.exe are checked. GWSL_vcxsrv is probably already checked

from gwsl-source.

In that case, WSL is malfunctioning. I'm sorry. I gtg though, I need to work on other things

hm, I get it. Thanks for trying to help all along the way

from gwsl-source.

Yes I just checked and both seems to be working now. Also before trying to open any linux apps I ticked every wsl related boxes under public in firewall

from gwsl-source.

😊 Happy the it got fixed. Can anything be done with the resolution?

from gwsl-source.

I can't change anything unfortunately. Normally it should have asked you to allow but it is possible the window was accidentally closed. I cannot automate the firewall because that could lead to bad security issues. But now I know how to handle this issue in the future. I will try to make a FAQ maybe.

from gwsl-source.

The linux apps section has lots that can be improved. It was an afterthought at first and it can be rewritten. To debug it could you use the shortcut creator to test if apps can run from there? There are multiple possible underlying issues.

from gwsl-source.

@Pololot64 So as you said I tried testing the shortcut creator. I tried creating a shortcut for Firefox (shortcut command: firefox) but after clicking on the created shortcut it doesn't seems to work, the loading cursor do shows up for a second or two but the app doesn't loads up.

from gwsl-source.

Ok. I have a formula for debugging :D. First, is anything in the log file? Second, did you change the default Linux shell? Third, what language and region is your computer set to? If it is none of these issues, it is related to a WSL problem most likely

from gwsl-source.

@Pololot64 I am new at these things but I will try my best. Yes, I had changed the default linux shell (most probably from "Debian x terminal emulator" to "xfce terminal") while I was customizing xfce but now when you said this I have changed it back to "Debian x terminal emulator". And then I shutdown the wsl and tried again on your software to open an app (from "linux apps" as well as using the shortcut) but it failed. I don't actually know where to check the log (If you can guide me then I can do it). My system language is English (US) and English (India) for keyboard, My region is India. Btw, Its midnight for me so I will be back in 7 hours😊

from gwsl-source.

Sleep well

from gwsl-source.

@Pololot64 What should I do next?

from gwsl-source.

Well, to find logs, I wrote this https://opticos.github.io/gwsl/tutorials/manual.html#finding-logs . If they are empty, it most likely means it is a WSL quirk... Are you using ZSH or FISH as a shell? By non default shell I meant something other than bash.

from gwsl-source.

@Pololot64 The service.log and dashboard.log are empty. I am using bash

from gwsl-source.

Strange. Something similar has only been reported once. I am making logging stronger in the next version though so maybe it will be easier to find after I release the update.

from gwsl-source.

@Pololot64 So, I guess I will wait for the next update then

from gwsl-source.

I pressed the release button on the Microsoft Store. It should be certified by Monday and then we can test again if you want

from gwsl-source.

Oh great, I will keep an eye on the arrival of the update 😊

from gwsl-source.

I think there is some issue with my microsoft store, some apps are not updating which includes gwsl. I guess I have to download the version from this github. btw, do you know what might be going on with my microsoft store and how to fix it.

from gwsl-source.

Idk. I don't even have the Microsoft store on my PC. I tried to get it back but never could... Maybe a couple reboots could help. Or running the Microsoft troubleshooter. Does the GWSL update show as available but is just not installing?

from gwsl-source.

when I click on "get updates" it shows gwsl have update but it doesn't downloads the update

from gwsl-source.

Strange. I guess it is just buggy

from gwsl-source.

So, I tried the latest version available on github but it doesn't seems to be working 😥

from gwsl-source.

I thought so. But that is ok because logging is better. Can you possibly open the logs and see what they say? You can access the logs through the systray menu now

from gwsl-source.

Service.log was empty but dashboard.log was there
dashboard.log

from gwsl-source.

What version of Windows 10 do you have?

from gwsl-source.

20H2

from gwsl-source.

Just wondering did you right click the systray icon and clear the configuration? Also, can you post the configuration file itself?

from gwsl-source.

Should I upload the setting.json file? or is there any other file and I don't think that I have cleared the logs nor the configuration

from gwsl-source.

settings.txt

from gwsl-source.

Hmm. That looks fine

from gwsl-source.

Weird, right? 😕

from gwsl-source.

I am pretty sure GWSL is functioning properly. This is possibly just caused by a slightly-broken WSL (which happens often it seems).

from gwsl-source.

hm understandable, Any idea to fix it. Most things developed by microsoft seems to have many issues 😅

from gwsl-source.

Maybe install a new distro (like Debian) and test with it.

from gwsl-source.

Hm I will try. But it feels pain to see my C drive getting filled. Does all the data related to a distro get deleted after deleting the application

from gwsl-source.

I have Ubuntu and Arch installed on Windows. both are not working for me as well

from gwsl-source.

@alok-debnath deleting GWSL does not affect WSL data. Removing WSL itself does. Also deleting a distro does

from gwsl-source.

Do you have different log output? Is this the same bug @lucasweiblen ?

from gwsl-source.

Do you have different log output? Is this the same bug @lucasweiblen ?

2021-01-24 12:51:19,498 - GWSL 1.3.7 - INFO - (run) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "/etc/init.d/dbus start &"
2021-01-24 12:51:19,498 - GWSL 1.3.7 - INFO - WSL OUTPUT >
2021-01-24 12:51:19,642 - GWSL 1.3.7 - INFO - (runo3) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;/bin/sh -c "echo $(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}')"
2021-01-24 12:51:19,642 - GWSL 1.3.7 - INFO - WSL OUTPUT > 172.19.128.1
2021-01-24 12:51:19,642 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:light DISPLAY=172.19.128.1:0 emacs&"
2021-01-24 14:54:43,387 - GWSL 1.3.7 - INFO - (run) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "/etc/init.d/dbus start &"
2021-01-24 14:54:43,387 - GWSL 1.3.7 - INFO - WSL OUTPUT >
2021-01-24 14:54:43,559 - GWSL 1.3.7 - INFO - (runo3) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;/bin/sh -c "echo $(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}')"
2021-01-24 14:54:43,560 - GWSL 1.3.7 - INFO - WSL OUTPUT > 172.21.80.1
2021-01-24 14:54:43,560 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:light DISPLAY=172.21.80.1:0 emacs&"
2021-01-24 14:55:19,488 - GWSL 1.3.7 - INFO - (run) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "/etc/init.d/dbus start &"
2021-01-24 14:55:19,488 - GWSL 1.3.7 - INFO - WSL OUTPUT >
2021-01-24 14:55:19,637 - GWSL 1.3.7 - INFO - (runo3) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;/bin/sh -c "echo $(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}')"
2021-01-24 14:55:19,637 - GWSL 1.3.7 - INFO - WSL OUTPUT > 172.21.80.1
2021-01-24 14:55:19,637 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:light DISPLAY=172.21.80.1:0 gtk3-demo&"
2021-01-24 14:55:54,438 - GWSL 1.3.7 - INFO - (run) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "/etc/init.d/dbus start &"
2021-01-24 14:55:54,438 - GWSL 1.3.7 - INFO - WSL OUTPUT > /bin/sh: line 1: /etc/init.d/dbus: No such file or directory
2021-01-24 14:55:54,596 - GWSL 1.3.7 - INFO - (runo3) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;/bin/sh -c "echo $(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}')"
2021-01-24 14:55:54,597 - GWSL 1.3.7 - INFO - WSL OUTPUT > 172.21.80.1
2021-01-24 14:55:54,597 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:light DISPLAY=172.21.80.1:0 /usr/bin/bvnc&"
2021-01-24 14:56:54,063 - GWSL 1.3.7 - INFO - (run) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "/etc/init.d/dbus start &"
2021-01-24 14:56:54,064 - GWSL 1.3.7 - INFO - WSL OUTPUT >
2021-01-24 14:56:54,229 - GWSL 1.3.7 - INFO - (runo3) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;/bin/sh -c "echo $(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}')"
2021-01-24 14:56:54,229 - GWSL 1.3.7 - INFO - WSL OUTPUT > 172.21.80.1
2021-01-24 14:56:54,229 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Arch . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:light DISPLAY=172.21.80.1:0 emacs &"
2021-01-24 15:01:44,713 - GWSL 1.3.7 - INFO - (run) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "/etc/init.d/dbus start &"
2021-01-24 15:01:44,713 - GWSL 1.3.7 - INFO - WSL OUTPUT >
2021-01-24 15:01:44,881 - GWSL 1.3.7 - INFO - (runo3) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;/bin/sh -c "echo $(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}')"
2021-01-24 15:01:44,881 - GWSL 1.3.7 - INFO - WSL OUTPUT > 172.21.80.1
2021-01-24 15:01:44,881 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:light DISPLAY=172.21.80.1:0 /usr/bin/emacs&"

from gwsl-source.

Again it might be WSL acting strange. Do apps work when run from the terminal when GWSL is running?

from gwsl-source.

Again it might be WSL acting strange. Do apps work when run from the terminal when GWSL is running

For me, apps do open and work though the terminal

from gwsl-source.

Alok, what happens when you run wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=$GTK_THEME:dark firefox&" in cmd.exe

from gwsl-source.

I got this nohup: ignoring input and appending output to 'nohup.out'

from gwsl-source.

And firefox did not open? Was GWSL running in the background?

from gwsl-source.

Sorry 😅, I thought it will trigger and start gwsl. Just now I tried after opening gwsl and it worked

from gwsl-source.

When I tried again I got this and firefox did not opened
/home/alokdebnath/.profile: line 41: syntax error near unexpected token `fi' /home/alokdebnath/.profile: line 41: `fi' nohup: ignoring input and appending output to 'nohup.out'

Any idea?🙄 I did clicked on "Set gtk to" option but then I reverted it back

from gwsl-source.

Ah, can you post the end of .profile relating to GWSL? (sorry this is taking a while to debug)

from gwsl-source.

I just copy pasted this wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=$GTK_THEME:dark firefox&"
I am grateful to help, since I only have online classes at least for now so I am free and will be happy to see this app working

from gwsl-source.

Also when I entered firefox in linux shell opened through the option in gwsl I got this Error: no DISPLAY environment variable specified

from gwsl-source.

Ah ok, so can you open the .profile file in linux in a text editor like nano?

from gwsl-source.

If you don't know how, open bash, navigate to the home directory (it should already be there) and type "nano .profile"

from gwsl-source.

Then scroll to the bottom of the file. Can you post a screenshot of what the bottom of the file looks like?

from gwsl-source.

Bash is the WSL terminal for Ubuntu

from gwsl-source.

from gwsl-source.

Does this make any sense? sorry

from gwsl-source.

from gwsl-source.

Can you delete from #GWSL_EXPORT_DISPLAY to the bottom? Also, do the same in .bashrc (which is another file). Then go into GWSL and re-export the display again. (just use baskspace to delete)

from gwsl-source.

/home/alokdebnath/.profile: line 41: syntax error near unexpected token fi' /home/alokdebnath/.profile: line 41: fi' nohup: > ignoring input and appending output to 'nohup.out'

This time I didn't get this error but also firefox did not opened

from gwsl-source.

Can you post the bottom of .profile again?

from gwsl-source.

from gwsl-source.

Can you now restart WSL?

from gwsl-source.

Done but still nothing

from gwsl-source.

wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=$GTK_THEME:dark DISPLAY=0.0.0.0:0 firefox&"

Try running this with 0.0.0.0 being your IP. You can find the correct IP by opening bash and typing echo $DISPLAY. Make sure the display port :0 is still at the end of the IP. And don't tell it to me :D

from gwsl-source.

wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=$GTK_THEME:dark DISPLAY=0.0.0.0:0 firefox&"

Still nothing

from gwsl-source.

In that case, WSL is malfunctioning. I'm sorry. I gtg though, I need to work on other things

from gwsl-source.

Update, I just had a thought. I know GWSL_vcxsrv.exe is allowed public access through the firewall. Is it possible that GWSL_instance.exe is not? Both must be granted public access.

from gwsl-source.

So, is there two different versions of gwsl? Is the one in store- vcxsrv and one in github- instance?

from gwsl-source.

They might be duplicated if you have had both the store and the github but no, they are both part of the same thing. GWSL_instance handles shortcuts. If it is not allowed, maybe it is what is causing the issue

from gwsl-source.

Yes. Start-menu , search for firewall --> allow an app through the windows firewall. Then chick change settings and scroll down to GWSL. Then you can change the rules for GWSL_instance. If there are duplicates just enable the disabled ones if any by checking the boxes under public.

from gwsl-source.

Just now I uninstalled the github version and installed the store version. Now this wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=$GTK_THEME:dark firefox&" works and also typing firefox in linux shell works like earlier

from gwsl-source.

Do shortcuts work? Or the app launcher?

from gwsl-source.

Cool. Wow that took a while to debug. Sorry about that :) Just don't do that to the firewall normally :) It is best to start with nothing and to enable till it works. That way you don't have unnecessary openings.

from gwsl-source.

@lucasweiblen Did you have this same issue?

from gwsl-source.

Cool. Wow that took a while to debug. Sorry about that :)

So was it the firewall issue?

from gwsl-source.

Well if it fixed the issue, yes

from gwsl-source.

I also have the problem, i try use cmd wsl -d Ubuntu-20.04 . ~/.profile;/bin/sh -c "GTK_THEME=$GTK_THEME:dark DISPLAY=0.0.0.0:0.0 firefox" it didn't work。

But i use cmd wsl -d Ubuntu-20.04 . ~/.profile;/bin/sh -c "GTK_THEME=$GTK_THEME:dark DISPLAY=$DISPLAY firefox" OR wsl -d Ubuntu-20.04 . ~/.profile;/bin/sh -c "GTK_THEME=$GTK_THEME:dark firefox ，it work

from gwsl-source.

@lucasweiblen Did you have this same issue?

I will confirm later, not on a windows machine right now. But I'm monitoring the issue. 😃

from gwsl-source.

@luoyuanbin16 It is because in the instructions above I said to replace that (0.0.0.0) with the correct IP for your specific machine. In the end, we found that the solution was to let GWSL through the firewall. It was just a missed setup step. Can you verify it is not being blocked by the firewall as well?

from gwsl-source.

I too am having a similar issue in which the applications never run from the shortcuts or app menu.
However, instead of the command being e.g. firefox change it to dbus-launch firefox and for whatever reason it will then work.

I had to do this for KDE Dolphin, but strangely if I launch dolphin in the terminal without anything fancy it works right away.

from gwsl-source.

Out of curiosity, what is your default shell set to?

from gwsl-source.

Out of curiosity, what is your default shell set to?

I'm not really sure. I cant get to my system right now. I am using Windows Terminal and for WSL I'm using ArchWSL by https://github.com/yuk7/ArchWSL

It's generally using a default environment, with the Desktop Environment being KDE Plasma 5.

from gwsl-source.

What happens when you run this echo "$SHELL"? (this prints what the default shell is)

from gwsl-source.

@luoyuanbin16 It is because in the instructions above I said to replace that (0.0.0.0) with the correct IP for your specific machine. In the end, we found that the solution was to let GWSL through the firewall. It was just a missed setup step. Can you verify it is not being blocked by the firewall as well?

I close all firewall，and it still not work. I find some msg in the View Log，maybe can help you find the reason.
2021-01-30 20:20:05,097 - GWSL 1.3.7 - INFO - (run) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "/etc/init.d/dbus start &" 2021-01-30 20:20:05,097 - GWSL 1.3.7 - INFO - WSL OUTPUT > your 131072x1 screen size is bogus. expect trouble 2021-01-30 20:20:05,447 - GWSL 1.3.7 - INFO - (runo3) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;/bin/sh -c "echo $(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}')" 2021-01-30 20:20:05,447 - GWSL 1.3.7 - INFO - WSL OUTPUT > your 131072x1 screen size is bogus. expect trouble 172.23.128.1 2021-01-30 20:20:05,451 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:light DISPLAY=your 131072x1 screen size is bogus. expect trouble 172.23.128.1:0 firefox&"

from gwsl-source.

@luoyuanbin16 It is because in the instructions above I said to replace that (0.0.0.0) with the correct IP for your specific machine. In the end, we found that the solution was to let GWSL through the firewall. It was just a missed setup step. Can you verify it is not being blocked by the firewall as well?

I close all firewall，and it still not work. I find some msg in the View Log，maybe can help you find the reason.
2021-01-30 20:20:05,097 - GWSL 1.3.7 - INFO - (run) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "/etc/init.d/dbus start &" 2021-01-30 20:20:05,097 - GWSL 1.3.7 - INFO - WSL OUTPUT > your 131072x1 screen size is bogus. expect trouble 2021-01-30 20:20:05,447 - GWSL 1.3.7 - INFO - (runo3) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;/bin/sh -c "echo $(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}')" 2021-01-30 20:20:05,447 - GWSL 1.3.7 - INFO - WSL OUTPUT > your 131072x1 screen size is bogus. expect trouble 172.23.128.1 2021-01-30 20:20:05,451 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:light DISPLAY=your 131072x1 screen size is bogus. expect trouble 172.23.128.1:0 firefox&"

from gwsl-source.

@luoyuanbin16 I don't have time to do the whole thing over again. Your logs do not show anything different. I don't know how to help

from gwsl-source.

For all the apps I am trying to start, I get this:

2021-03-15 14:16:51,595 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:dark DISPLAY=your 131072x1 screen size is bogus. expect trouble
172.21.176.1:0 gnome-control-center&"
2021-03-15 14:17:16,785 - GWSL 1.3.7 - INFO - (run) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "/etc/init.d/dbus start &"
2021-03-15 14:17:16,785 - GWSL 1.3.7 - INFO - WSL OUTPUT > your 131072x1 screen size is bogus. expect trouble
2021-03-15 14:17:17,597 - GWSL 1.3.7 - INFO - (runo3) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;/bin/sh -c "echo $(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}')"
2021-03-15 14:17:17,597 - GWSL 1.3.7 - INFO - WSL OUTPUT > your 131072x1 screen size is bogus. expect trouble
172.21.176.1
2021-03-15 14:17:17,597 - GWSL 1.3.7 - INFO - (runos) WSL SHELL $ wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:dark DISPLAY=your 131072x1 screen size is bogus. expect trouble
172.21.176.1:0 tilix&"

from gwsl-source.

First of all @iongion gnome-control center is hard to get working and is not a good app to test with. Tilix does normally work. What happens if you run TIlix from the Ubuntu shell directly? (Make sure GWSL is still running in the background)

from gwsl-source.

If I type in the shell prompt with this in my .profile

export GDK_SCALE=1
export QT_SCALE_FACTOR=1
export GDK_DPI_SCALE=-1
export DISPLAY=$(awk '/nameserver / {print $2; exit}' /etc/resolv.conf 2>/dev/null):0
export LIBGL_ALWAYS_INDIRECT=1

then it runs.

If I click the tilix app in the menu, nothing happens. In fact, none of the apps listed in the menu work

from gwsl-source.

What happens when you click the link icon next to any of the apps listed? For example, for Tilix what is in the Shortcut Command box?

from gwsl-source.

from gwsl-source.

What happens when you run this in cmd.exe? wsl.exe ~ -d Ubuntu-20.04 . ~/.profile;nohup /bin/sh -c "GTK_THEME=Adwaita:dark DISPLAY=172.21.176.1:0 tilix&"

from gwsl-source.

all good - it starts

from gwsl-source.

Strange. That is the command that GWSL is running...

from gwsl-source.

Wait. Did you allow GWSL_instance.exe to have public access through the firewall? @iongion That is probably the issue

from gwsl-source.

from gwsl-source.

That's ok. Yep I relate. I tried to make it add the rule automatically but Microsoft did not want that in the store :)

If you want you can allow it through Control Panel --> System and Security --> Allow an app through Windows firewall. Make sure the public boxes of GWSL_service.exe and GWSL_instance.exe are checked. GWSL_service is probably already checked

@Pololot64 not working =)

from gwsl-source.

@genemators I don't have any of your debug info yet but you can look around this issue and see if your issue is caused by some already known problem. Most problems I solve are duplicates.

from gwsl-source.

I have had GWSL installed for months, and could never get it to work...
Allowing GWSL through windows firewall as per pololot64's comments did the trick!
Don't know why this isn't getting set up automatically, but all good, thanks for the tip!

from gwsl-source.