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

aw-qt not starting on Windows 10 (seems like #161) #444

Closed
2 tasks done
heliocarbex opened this issue Jun 22, 2020 · 10 comments
Closed
2 tasks done

aw-qt not starting on Windows 10 (seems like #161) #444

heliocarbex opened this issue Jun 22, 2020 · 10 comments
Labels
invalid Nothing to fix, not an actual bug, etc. type: bug

Comments

@heliocarbex
Copy link

heliocarbex commented Jun 22, 2020

  • I am on the latest ActivityWatch version.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • OS version and name: MS Windows 10
  • ActivityWatch version: 0.9.2

Describe the bug

When trying to start aw-qt.exe the following message appears: "Failed to execute script main" and the application crashes.

This appears to be a duplicate bug, but to another OS. So, I can't apply the same solution. I think that the same proble happend here at Linux: #161

To Reproduce

Steps to reproduce the behavior:

  1. Go to ".\activitywatch folder"
  2. Click "aw-qt.exe"
  3. See error "Failed to execute script main"

Expected behavior

Activity Watch should start and I should see in the browser all the graphs at http://localhost:5600.

Documentation

Log file aw-qt_2020-06-22T13-59-57.log:
2020-06-22 13:59:57 [INFO ]: Starting module aw-server (aw_qt.manager:49)

Log file aw-watcher-afk_2020-03-02T10-35-38.log
2020-03-02 10:35:38 [INFO ]: aw-watcher-afk started (aw_watcher_afk.afk:53)
2020-03-02 10:35:44 [WARNING]: Not connected to server, 0 requests in queue (aw_client.client:380)
2020-03-02 10:36:00 [WARNING]: Not connected to server, 2 requests in queue (aw_client.client:380)
2020-03-02 10:36:15 [WARNING]: Not connected to server, 3 requests in queue (aw_client.client:380)
2020-03-02 10:36:30 [WARNING]: Not connected to server, 4 requests in queue (aw_client.client:380)
2020-03-02 10:36:45 [WARNING]: Not connected to server, 6 requests in queue (aw_client.client:380)
2020-03-02 10:37:01 [WARNING]: Not connected to server, 7 requests in queue (aw_client.client:380)
2020-03-02 10:37:20 [WARNING]: Not connected to server, 8 requests in queue (aw_client.client:380)

@ErikBjare
Copy link
Member

Do you run ActivityWatch using the zip or using the installer?

Can you run aw-qt.exe from the command line and report the output?

@heliocarbex
Copy link
Author

Using the zip. I tried to run using CLI, but the exe is not producing any output.

@heliocarbex
Copy link
Author

Do you recommend to use the installer version?

@ErikBjare
Copy link
Member

Using the zip. I tried to run using CLI, but the exe is not producing any output.

Try running aw-server.exe from the command line, that should hopefully give you some output.

Do you recommend to use the installer version?

It really shouldn't make a difference, since the installer uses the same files as those in the zip. But please try the installer version anyway, maybe you've extracted the files over an older version or something.

@heliocarbex
Copy link
Author

Dear ErikBjare,

There is no aw-server.exe in my activity watch folder. Here I'm showing the search results for .exe files:

image

@johan-bjareholt
Copy link
Member

In the zip there is a aw-server folder which contains aw-server.exe (same thing goes for the watchers, they all have their own folder except for aw-qt).

@heliocarbex
Copy link
Author

In the zip there is a aw-server folder which contains aw-server.exe (same thing goes for the watchers, they all have their own folder except for aw-qt).

For me, there is no .exe inside aw-server folder, XD
image

@johan-bjareholt
Copy link
Member

johan-bjareholt commented Jul 4, 2020

@heliocarbex It is there in the original zip file so then you have either done something wrong when unpacking it or your anti-virus has removed it automatically or something like that.

@heliocarbex
Copy link
Author

Right, I will check it out.

@ErikBjare
Copy link
Member

I'm assuming the aw-server.exe has been deleted by an AV system or something, so closing the issue.

@ErikBjare ErikBjare added the invalid Nothing to fix, not an actual bug, etc. label Jul 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Nothing to fix, not an actual bug, etc. type: bug
Projects
None yet
Development

No branches or pull requests

3 participants