motion crashes when launched because of ffmpeg library

[Avinash Meetoo]

When motion starts, it crashes with an illegal instruction:

[33457800:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[33457800:motion] [NTC] [ALL] config_camera: Processing camera config file /etc/motion/camera1.conf
[33457800:motion] [NTC] [ALL] config_camera: Processing camera config file /etc/motion/camera2.conf
[33457800:motion] [NTC] [ALL] motion_startup: Motion 4.1.1 Started
[33457800:motion] [NTC] [ALL] motion_startup: Logging to file (/var/log/motion/motion.log)
Illegal instruction

Both of my cameras are old MJPEG cameras. Motion handle them using ffmpeg libraries internally. I have spent some time looking at the crash and it happened on the day my ffmpeg libraries were updated.

Motion worked fine with the following:

2021-10-17 16:54:37 status installed libavutil56:armhf 7:4.1.6-1~deb10u1+rpt2
2021-10-17 16:54:45 status installed ffmpeg:armhf 7:4.1.6-1~deb10u1+rpt2
2021-10-17 16:54:45 status installed libavcodec58:armhf 7:4.1.6-1~deb10u1+rpt2
2021-10-17 16:54:45 status installed libavdevice58:armhf 7:4.1.6-1~deb10u1+rpt2
2021-10-17 16:54:45 status installed libavfilter7:armhf 7:4.1.6-1~deb10u1+rpt2
2021-10-17 16:54:45 status installed libavformat58:armhf 7:4.1.6-1~deb10u1+rpt2
2021-10-17 16:54:45 status installed libavresample4:armhf 7:4.1.6-1~deb10u1+rpt2

and it has started crashing when the following upgrades were made:

2021-10-24 08:50:45 status installed ffmpeg:armhf 7:4.1.8-0+deb10u1+rpt1
2021-10-24 08:50:45 status installed libavcodec58:armhf 7:4.1.8-0+deb10u1+rpt1
2021-10-24 08:50:45 status installed libavdevice58:armhf 7:4.1.8-0+deb10u1+rpt1
2021-10-24 08:50:45 status installed libavfilter7:armhf 7:4.1.8-0+deb10u1+rpt1
2021-10-24 08:50:45 status installed libavformat58:armhf 7:4.1.8-0+deb10u1+rpt1
2021-10-24 08:50:45 status installed libavresample4:armhf 7:4.1.8-0+deb10u1+rpt1
2021-10-24 08:50:45 status installed libavutil56:armhf 7:4.1.8-0+deb10u1+rpt1

Of course, there might be a bug in Motion but I suspect that the bug is in the ffmpeg libraries.

Is it possible to downgrade to 4.1.6-1~deb10u1+rpt2 in the meantime? I've tried looking for the packages online but they are not in the official repositories anymore.

[Avinash Meetoo (avinash)]

I have downgraded ffmpeg to 4.1.6-1~deb10u1+rpt2 and motion is working fine.