Incorrectly exiting on logout and generating huge log files

[zerowhybr]

• [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: Arch Linux 5.12.14, KDE Plasma 5.22.2 on X11
• ActivityWatch version: 0.11.0

Describe the bug

Constant error messages logged to ~/.local/share/sddm/xorg-session.log, which ends up filling up local storage very quickly, especially on already low space storage devices.

To Reproduce

1. Start ActivityWatch normally
2. Log out
3. Log back in
4. Some errors pops up telling you the program quit unexpectedly (aw-watcher and some others)
5. Constant error messages are now flooding xorg-session.log

Expected behavior

The program should quit normally after logout and start again on login

Documentation

Log of errors in xorg-session.log: https://0bin.net/paste/Uv76U7hI#orjz0x57Es5-Mq/+hENWrmsTpsDy8842VUmKyYKKSdw If more lines of the log or any more information is necessary I can provide it.

[github-actions[bot]]

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

[sonofhypnos]

I am having the same issue. logs: https://pastebin.com/25WNLib6 OS: Pop OS with Regolith

I am launching aw-qt from my i3-config like this: exec ~/.local/opt/activitywatch/aw-qt

[ErikBjare]

Caused by https://github.com/ActivityWatch/aw-qt/issues/49

[s0ren]

I see the same with aw-watcher-window Now I have a 267,7 Gb logfile in ~/.cache/activitywatch/log/aw-watcher-window/aw-watcher-window_2022-12-03T21-44-20.log

[ErikBjare]

This has been fixed and will be in the next release: https://github.com/ActivityWatch/activitywatch/issues/756#issuecomment-1292126836

[ErikBjare]

Or wait, actually, the above fix might not address xorg-session.log getting spammed.

Reopening and will revisit after the next release is out.

[s0ren]

Ok. Nice, I think the reason for these excessive log messages, comes from problems with running the qt app. Now i just start the python script, and thats fine.

Den fre. 9. dec. 2022 kl. 13.41 skrev Erik Bjäreholt < @.***>:

This has been fixed and will be in the next release: #756 (comment) https://github.com/ActivityWatch/activitywatch/issues/756#issuecomment-1292126836

— Reply to this email directly, view it on GitHub https://github.com/ActivityWatch/activitywatch/issues/629#issuecomment-1344263854, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAT6VPK66ENLFYZUVF7JBTTWMMSIVANCNFSM47XVVC3Q . You are receiving this because you commented.Message ID: @.***>