Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GWSL Service keeps crashing on Startup #183

Open
J4yTr1n1ty opened this issue May 28, 2024 · 4 comments
Open

GWSL Service keeps crashing on Startup #183

J4yTr1n1ty opened this issue May 28, 2024 · 4 comments

Comments

@J4yTr1n1ty
Copy link

On a fresh installation of the latest version from the Microsoft Store starts up, however the Service keeps crashing with the following Message:

image

The service.log file lists the following Error:

2024-05-28 08:38:41,816 - __main__ - ERROR - Exception occurred in main loop
Traceback (most recent call last):
  File "main.py", line 663, in main
SystemExit
2024-05-28 08:38:42,797 - __main__ - ERROR - Exception occurred - Cannot Start Service. Make sure the settings file is not corrupted.
Traceback (most recent call last):
  File "main.py", line 663, in main
SystemExit

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "main.py", line 757, in <module>
  File "main.py", line 681, in main
SystemExit
@mentalisttraceur
Copy link

I am having a silent version of this: no pop-up, but the exact same logs. (Including with fresh/reset config.)

Strangely, xclock from About in the dashboard works.

@mentalisttraceur
Copy link

mentalisttraceur commented Aug 30, 2024

Ah, looks like my version of this issue is a non-problem. After I worked around #184 everything started working for me, despite this error in the logs.

@mentalisttraceur
Copy link

Okay, now I've observed this bug, while manually fiddling. In my case, the issue was that I was launching and killing gwsl.exe interactively, and ending up with two instances at once (maybe one didn't get killed or was in the process of shutting down and hadn't yet let go of some lock or network port or whatever).

You can check if this is what's happening for you by seeing if there are two GWSL icons in the task bar:

image

One thing I noticed is that once I was in this state, hitting "yes" didn't actually fix it - since there's still two instances running, when you agree to restart, you're right back at the same problem.

If this is your situation, try hitting "No" to the restart prompt until it stops popping up, maybe also manually clear out any lingering instances in the task bar, and then start GWSL once manually.

@mentalisttraceur
Copy link

One other way I triggered this was

  1. set up automatic silent startup,

  2. double-clicked a gwsl.exe --r ... shortcut.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants