activitywatch icon indicating copy to clipboard operation
activitywatch copied to clipboard

Mac M1 - Missing time

Open ChillarAnand opened this issue 1 year ago • 11 comments

  • [x] I am on the latest ActivityWatch version.
  • [x] I have searched the issues of this repo and believe that this is not a duplicate.
  • OS name and version: MacOS,
  • ActivityWatch version: 0.12.2

Describe the bug

When system is booted, all modules are selected and time is tracked properly.

Modules are getting "unselected" after a while and time is not tracked properly.

Screenshot 2024-05-02 at 16 40 36

ChillarAnand avatar May 02 '24 11:05 ChillarAnand

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! 🙏

github-actions[bot] avatar May 02 '24 11:05 github-actions[bot]

That's due to the watcher crashing. It should be fixed and more stable in v0.12.3b15.

When a watcher crashes, there should be a popup notifying that it did, offering the option to restart it. But sometimes those popups get hidden under other windows on macOS (or seemingly don't show up at all).

ErikBjare avatar May 02 '24 11:05 ErikBjare

@ErikBjare Thanks for the quick reply.

How can I install v0.12.3b15 on Mac?

ChillarAnand avatar May 02 '24 12:05 ChillarAnand

I found a dmg file under Release section. I have installed https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.3b16

ChillarAnand avatar May 02 '24 12:05 ChillarAnand

As mentioned in the release notes, v0.12.3b16 is unstable (as you may notice). Use v0.12.3b15 instead.

ErikBjare avatar May 02 '24 12:05 ErikBjare

Unfortunately, I am observing the same issue on v0.12.3b15 as well.

Screenshot 2024-05-02 at 21 10 47

ChillarAnand avatar May 02 '24 15:05 ChillarAnand

You may have running background processes that have survived, preventing a second instance from starting. (This should also show a popup, I'm surprised you don't seem to get one?)

Check ps -aux | grep aw- in the terminal. Quit ActivityWatch and kill all processes, then start it again.

ErikBjare avatar May 02 '24 16:05 ErikBjare

You may have running background processes that have survived, preventing a second instance from starting. (This should also show a popup, I'm surprised you don't seem to get one?)

No popups at all.

I have restarted the system. Will monitor for some time and let you know.

Thanks @ErikBjare for the help!

ChillarAnand avatar May 02 '24 16:05 ChillarAnand

The frequecny of crashing has reduced but it is still happening. No pop-ups yet.

This seems to happen when I lock the screen, keep the Mac idle for ~10 hours, and unlock it again.

Unfortunately, aw-notify is not working on Mac. I wrote a python script and setup a cron job for notification.

https://github.com/ActivityWatch/aw-notify/issues/2

https://avilpage.com/2024/05/screen-time-alerts-from-activity-watch.html

ChillarAnand avatar May 08 '24 06:05 ChillarAnand

The frequecny of crashing has reduced but it is still happening. No pop-ups yet.

This seems to happen when I lock the screen, keep the Mac idle for ~10 hours, and unlock it again.

Unfortunately, aw-notify is not working on Mac. I wrote a python script and setup a cron job for notification.

ActivityWatch/aw-notify#2

https://avilpage.com/2024/05/screen-time-alerts-from-activity-watch.html

Same question, aw-notify cannot work. Don't know what "run it from a signed bundle" means.

2024-06-11 16:50:03 [WARNING]: Authorisation denied: The operation couldn’t be completed. (UNErrorDomain error 1.)  (desktop_notifier.macos:196)
2024-06-11 16:50:03 [WARNING]: The operation couldn’t be completed. (UNErrorDomain error 1.): None  (desktop_notifier.macos:304)

baker221 avatar Jun 11 '24 09:06 baker221