awatcher: Stops working randomly
Running Archlinux + Hyprland.
I’m using bundled awatcher and starting it like:
exec-once = telegram-desktop & awatcher
It starts well and runs at first, then randomly it crashes. I don’t have a log or something unfortunately, if you can guide me how to get it I can provide that.
Example:
as you can see I was not AFK and was on meet but all of a sudden awatcher stops recording. Weird thing is the server works all the time, I can access localhost:5600 all the time.
This is an example of random day, it happens almost every day.
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 1
- Comments: 16 (12 by maintainers)
I also noticed this issue and there seems to be two issues at play:
watcher.run_iteration(fixed by timeout)[2024-05-19 22:04:58.559502 [31mERROR[0m watchers::watchers] Error on active window iteration: GetPropertyReply[_NET_WM_NAME] failed(should be fixed by commenting out X11 window watcher but have yet to test it)Issue doesn’t occur for me on
(my computer was suspended at the blank point in the middle)
v0.2.7of awatcher (installed as module) with hyprlandv0.40.0-1If you use Gnome and given the symptoms, it means that DBus call to
org.gnome.shell.extensions.FocusedWindowhangs at some moment. There is only that call (and reporting to AW server).@luisgerhorst Your change looks good and universal to hopefully exclude similar problems in this and other watchers. It’s simple and free to try anyway. I can commit the change in a few days for
0.2.7, or preferably merge your PR if you push it (with other watchers enabled). Thanks regardless ❤️@luisgerhorst why could it be? E.g. why have you added timeouts in a couple places, and removed the reconnect attempts for Gnome watchers? I see that your changes only affect the watcher loading/initializing but I’ve got an impression that the failures happen long after loading, during normal functioning.
I’ve been using @luisgerhorst’s fork since May 3, and the problem has not happened since then.
Just wanted to let you know that I’ve now built awatcher from source (all worked like a charm) and disabled some of the other watchers. I’ve now been running that debug build for 2 weeks and have not been able to reproduce the issue since. I will continue to debug and try to pinpoint it.
Here’s the changes I made: https://github.com/luisgerhorst/awatcher/commit/26d2f2e67bcd03b4c291dee150fb4cadeeae76a7 - However, it could also be just a coincidence at this point…
Here you go:
Hardware Information:
Software Information:
In extensions, I see a 6 behind the name of https://github.com/flexagoon/focused-window-dbus, not sure if that is the version.
I also get vastly wrong usage times in the overview of the web interface.
A also see this happening, with both standalone and bundled versions. I noticed the following: