Open SchittBull opened 1 year ago
Hi there! As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct. Thanks a bunch for opening your first issue! 🙏
Thanks for also adding the log :) It seems it's the same problem as in https://github.com/ActivityWatch/activitywatch/issues/873.
From https://github.com/ActivityWatch/activitywatch/issues/873#issuecomment-1555491837:
By reading the change log, the new version switched from WMI to Win32 API (https://github.com/ActivityWatch/aw-watcher-window/pull/83) to obtain a window in focus; I guess it fixed the issue of high CPU usage of WMI Provider Host. That should be the cause of the behaviour change.
It is expected for a program without elevated rights to be unable to access programs with elevated rights. But this might not be a desired behaviour of ActivityWatch.
Is this Windows OS related ?
Describe the bug
Since v0.12.1, parsec.app is not getting tracked anymore. it worked on v0.12.1 tested on 2 machines
To Reproduce
Expected behavior
parsec being tracked like any other program
Documentation
an excerpt from the log that continues for ever like this: