Tobias Göbel

For the moment i#m not in reach of an linux system. But i'll investigate in this tomorrow or monday (depends on when i'm in reach of one) but i didn't...

basically it's gdb ../emulationstation (when you are in the build directory) r (to run the programm when crash occours "bt" to backtrace. and i'm neither, those are the only two...

So i tested, and couldn't reproduce your problem.. could you please attach a backtrace?

+1 also on arch, and the problems seems to come from one of the updates of the last month(s). Zoneminder runned perfectly for months, then i recently installed long waited...

The problem seems to only happen with Docker 23.0.1. Docker 20.10.23 seem to work fine. So i think it will be something that has changed from docker 20.10.23 to docker...

Problem persists with Docker 24.0.2 i have no clue how this problem could be solved.

Thanks for the hint. But I don't think it is related (at least in my case). I deploy with portainer, to a 3 cluster docker swarm (although this stack is...

can confirm. as a quick test i updated to docker 24.0.5 and replaced the file inside the container with one where www-run is replaced with root. Zoneminder starts without problems...

I modified the sensor.py to fix some values, and have a fix for the divided by zero problems. ``` --- sensor.py.old 2025-05-09 22:03:52.554780794 +0200 +++ sensor.py 2025-05-09 22:03:25.327192013 +0200 @@...

[sensor.txt](https://github.com/user-attachments/files/20129248/sensor.txt) just rename it to sensor.py *.py is not allowed in comments..