segfault with /etc/motion/motion.conf unreadable

[Lars Kr. Lundin]

Binary package hint: motion

Images are produced OK with /etc/motion/motion.conf readable.
Tested with ancient 3com HomeConnect webcam, see attachment.
Other software (camorama, skype) does not detect camera, xsane does.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: motion 3.2.11-1ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
SourcePackage: motion
Uname: Linux 2.6.28-15-generic i686

[Lars Kr. Lundin (v-launchpad-lklundin-dk)]

$ tail -f /var/log/messages
Sep 19 13:23:01 h2 kernel: [86584.168010] usb 3-2: new full speed USB device using ohci_hcd and address 5
Sep 19 13:23:01 h2 kernel: [86584.384410] usb 3-2: configuration #1 chosen from 1 choice
Sep 19 13:23:01 h2 kernel: [86584.387385] ViCam based webcam connected
Sep 19 13:23:01 h2 kernel: [86584.387423] ViCam webcam driver now controlling video device 0
Sep 19 13:23:18 h2 motion: [0] Not config file to process using default values
Sep 19 13:23:18 h2 motion: [0] Motion 3.2.11 Started
Sep 19 13:23:18 h2 motion: [0] ffmpeg LIBAVCODEC_BUILD 3410688 LIBAVFORMAT_BUILD 3414017
Sep 19 13:23:18 h2 kernel: [86601.230591] usb 3-2: firmware: requesting vicam/firmware.fw
Sep 19 13:23:18 h2 motion: [1] Resizing pre_capture buffer to 1 items
Sep 19 13:23:19 h2 kernel: [86602.110415] motion[21379]: segfault at b639e000 ip 08057c3b sp b6b9ca30 error 4 in motion[8048000+32000]

[Pander (pander)]

Probably, this has been fixed, see https://github.com/Motion-Project/motion/issues?q=is%3Aissue+is%3Aclosed+segfault

This was also reported for a version from 2009 and is I think no longer relevant. If that is the case, this bug can be closed.