I’m running a rather unique setup, and ActivityWatch may not be compatible. Let’s tackle the easy one first.
I’m using Debian, and my browser is Ungoogled Chromium (a modification of Chromium that removes as much Google code as possible). The executable is
/usr/bin/chromium. I have the ActivityWatch Chrome plugin installed and
aw-qt running, but no activity is being captured when I look in the web UI. If I stop
aw-qt, the Chrome plugin sends a notification “Unable to send event to server,” so it’s clearly connecting properly. Why am I not seeing any browser activity? Perhaps I misunderstand how the watcher works.
On to the complicated one. I use an OS called Qubes. It is a Xen-based client hypervisor where you can set up multiple, separate, self-contained VMs. All applications then run in the same window manager (much like VMware’s Seamless or Unity mode where applications launched inside a VM behave natively to the host OS’s window manager). I have ActivityWatch set up inside the Debian VM I use for work which is what I want to be watching. However, it’s not able to collect any data. It IS able to detect if I’m AFK or not, but that’s all.
aw-qt is showing an endless loop of warnings in the console:
[WARNING]: window_prop was None (aw_watcher_window.xlib:23)
I’m assuming that this has to do with the way Qubes works and ActivityWatch needs to be running on the host Xen system in order to watch active windows. However, I wondered if there might be a way to get around this.
Thanks for your help!