Comment 12 for bug 1946521

I can confirm that motion from jammy-proposed has fixed the bug for me.

Test done:

Install motion on a jammy installation.
confirm that motion service did not start and the issue is seen.

Add jammy-proposed to apt sources
update motion from jammy-proposed
check that the motion.service is running

$ systemctl status motion.service
● motion.service - Motion detection video capture daemon
     Loaded: loaded (/lib/systemd/system/motion.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2024-05-04 19:20:55 BST; 8s ago
       Docs: man:motion(1)
   Main PID: 3250 (motion)
      Tasks: 4 (limit: 9436)
     Memory: 19.0M
        CPU: 118ms
     CGroup: /system.slice/motion.service
             └─3250 /usr/bin/motion

Test result: the issue with motion has been fixed.

Package tested:

$ apt-cache policy motion
motion:
  Installed: 4.3.2-1ubuntu0.1
  Candidate: 4.3.2-1ubuntu0.1
  Version table:
 *** 4.3.2-1ubuntu0.1 500
        500 http://gb.archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 Packages
        100 /var/lib/dpkg/status
     4.3.2-1 500
        500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages