Can't find the path to aw-qt.exe on windows 11
arnishbaruah opened this issue · comments
I placed the aw-watcher-mpv.exe in C:\Program Files\ActivityWatch\aw-watcher-mpv as I couldn't figure out the location of aw-qt.exe. Hence the aw-watcher-mpv doesn't appear in modules. How to find the path to aw-qt.exe on windows 11?
Do you not have it at C:\Program Files\ActivityWatch\aw-qt.exe? If so, I'm not sure - perhaps try:
- rightclicking the start menu icon for ActivityWatch, "Open file location"
- This will get you the shortcut file, so rightclick it and "Open file location again", and that should get you the
aw-qt.exe.
I'm on Windows 10, not 11, so can't test myself.
Another way that should work is opening the Task Manager, finding aw-qt.exe in the Details tab, and doing Open File Location on it.
This is the location : "C:\Users<username>\AppData\Local\Programs\ActivityWatch"
My mpv watcher : "C:\Users<username>\AppData\Local\Programs\ActivityWatch\aw-watcher-mpv"
My mpv history location : "C:\Users<username>\AppData\Roaming\mpv\mpv-history"
There is no tick mark when I click on the mpv watcher module. There is no tick mark even after adding it to autostart.
There is no tick mark when I click on the mpv watcher module
So you do see aw-watcher-mpv among the modules now, and before you didn't? That's progress - if it doesn't stay checkmarked after clicking on it, that means it crashes on launch.
The most likely cause is an incorrect or unspecified path to the history location, but you can check by rightclicking the tray icon, "Open log folder", and looking at the latest log in the aw-watcher-mpv subfolder. It should contain some error message, hopefully describing what's wrong.
This is the only line in my toml file log_folder = "C:\Users<username>\AppData\Roaming\mpv\mpv-history" and there is no aw-watcher-mpv subfolder in log folder.
I looked over the code and I don't see anything that might cause it to crash before setting up logging (and so not leave a log of that), so not sure how this can happen. The next step would be to try running it with a debugger, but I can't replicate the issue locally for that.
You can try running it in a windows 11 VM