Help installing Motionplus

Raspberry pi zero 2w with latest Manjaro, connected a pi camera module 2

I was wondering if anybody managed to properly install motionplus.
Here’s what I installed as dependencies:
ffmpeg gcc-libs glibc libjpeg-turbo libmicrohttpd libpulse alsa-lib libwebp libcamera libcamera-tools fftw with ./configure --without-v4l2 --with-libcam --without-opencv --without-pulse --without-alsa --without-mariadb --without-mysql --without-pgsql --without-sqlite3 .
It builds without errors but when I run it I’m getting errors such as:

[0:25:15.011283010] [2958] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
[0:25:15.011618012] [2958]  INFO Camera camera_manager.cpp:284 libcamera v0.2.0
[0:25:15.167953508] [2960]  WARN RPiSdn sdn.cpp:39 Using legacy SDN tuning - please consider moving SDN inside rpi.denoise
[0:25:15.173070456] [2960]  WARN RPI vc4.cpp:347 Mismatch between Unicam and CamHelper for embedded data usage!
[0:25:15.174379993] [2960]  INFO RPI vc4.cpp:401 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media1 and ISP device /dev/media0
[0:25:15.176886618] [2958]  INFO Camera camera.cpp:1183 configuring streams: (0) 1280x720-YUV420
[0:25:15.177604746] [2960]  INFO RPI vc4.cpp:559 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 1920x1080-SBGGR10_1X10 - Selected unicam format: 1920x1080-pBAA
[0:25:15.182406641] [2963]  WARN IPARPI ipa_base.cpp:715 Could not set AF_MODE - no AF algorithm
[0:25:15.182547787] [2963]  WARN IPARPI ipa_base.cpp:1172 Could not set LENS_POSITION - no AF algorithm
[0:25:15.182642840] [2963]  WARN IPARPI ipa_base.cpp:1079 Could not set AF_RANGE - no focus algorithm
[0:25:16.296562228] [2963] FATAL default ipa_base.cpp:396 assertion "it != buffers_.end()" failed in prepareIsp()
Backtrace:
libcamera::ipa::RPi::IpaBase::prepareIsp(libcamera::ipa::RPi::PrepareParams const&)+0x550 (/usr/lib/libcamera/ipa_rpi_vc4.so [0x0000ffffac1bd800])
libcamera::Object::message(libcamera::Message*)+0x98 (/usr/lib/libcamera-base.so.0.2.0 [0x0000ffffb92ab168])
libcamera::Thread::dispatchMessages(libcamera::Message::Type)+0x218 (/usr/lib/libcamera-base.so.0.2.0 [0x0000ffffb92ade6c])
libcamera::EventDispatcherPoll::processEvents()+0x58 (/usr/lib/libcamera-base.so.0.2.0 [0x0000ffffb92a1f98])
libcamera::Thread::exec()+0x9c (/usr/lib/libcamera-base.so.0.2.0 [0x0000ffffb92ad6fc])
execute_native_thread_routine+0x1c (/usr/src/debug/gcc-build/aarch64-unknown-linux-gnu/libstdc++-v3/include/bits/unique_ptr.h:95)
??? [0x0000ffffb65e0aec] (/usr/lib/libc.so.6 [0x0000ffffb65e0aec])
??? [0x0000ffffb664a5dc] (/usr/lib/libc.so.6 [0x0000ffffb664a5dc])

and it core dumps.
Thanks for any help

I just installed this to try it out (I use motion, but hadn’t heard of motionplus).

I found that motionplus wouldn’t build, but motionplus-git would.

I’m not seeing any segfaults, but I noticed that it didn’t like quite a few of the options in my existing configuration file. Are you migrating from an existing motion installation? If so, it might be worth creating a fresh configuration file from the new templates in /etc/motionplus in case something you’ve got there is causing the problem. Though I can’t guarantee this will work.

I’m building it from git sources, motionplus-git sounds like AUR where arch=x86_64 not aarch64

I managed not to notice that you were on a Raspberry Pi. I suspect the problem is somehow related to the ARM architecture. Perhaps you’d be better off with the “original” motion?