MichaIng

Are there probably some invalid image files, like null byte files generated from the earlier motionEye version which was affected by the issue? Since `ghcr.io/motioneye-project/motioneye@sha256:3a38c03592203b6039873be026238a625da3f7bab099b93faf3024542dfae14c` worked perfectly as you stated,...

Code to check: https://github.com/motioneye-project/motioneye/blob/dev/motioneye/mediafiles.py#L329 Maybe it attempts to generate an image every X seconds, which equals around 10 MiB in your case, and the first is done at X seconds,...

Then I am pretty sure `ffmpeg` now errors out in this case. I guess we would need to check the movie duration then, and choose e.g. the rounded down middle...

Radarr dropped Mono support with v4, and proves dotnet based downloads since v3, which we use since then for all architectures but ARMv6 (which is not supported by dotnet), so...

Do you use a Debian Bullseye system?

Okay, then it is most certainly this issue: https://wiki.servarr.com/radarr/faq#radarr-wont-start-on-debian-11-or-older-systems-due-to-sqlite-version Same happened to Lidarr and Prowlarr some weeks ago. Need to keep that in mind when other Servarr apps get their...

It seems BoringSSL found some alternative fix: - https://github.com/google/boringssl/commit/63c8e81 - https://github.com/google/boringssl/commit/2d3fbe0

Got it, thought it might be all related to the same underlying issue, and hence potentially a way to fix the issue without performance regression.

It seems to be originating from regulator code, similar reports for sunxi boards exist: https://lkml.org/lkml/2020/10/21/558 Might be related to device tree nodes which are disabled, or not in use. To...

Since it is all Python scripts, you could also modify them after regular install. Of course an update would overwrite it, but that is the same with installing from a...