I'm trying to get both a USB gamepad and the webcam in my laptop working with webcamd. I'm running Plasma 5 on FreeBSD 12.1-RELEASE.
I have hald_enable="YES" in my /etc/rc.conf.local file. The RC script supplied with webcamd detects whether HAL is enabled and, if it is, automatically adds the -H flag (which enabled HAL support) to the parameters passed to webcamd upon starting. This is probably fine if everything is working as expected, but that isn't the case.
webcamd was not creating /dev/input/js0 for my gamepad or /dev/video0 for my webcam when I started it via the RC script. However, when I started webcamd directly from the commandline, it did. So I tried passing the -H flag to webcamd, and it just kept emitting the message "Waiting for HAL connection." on the console.
For whatever reason, webcamd is never connecting to HAL and just gets stuck waiting for a connection to HAL thus never creating any device nodes. So the current workarounds I've found, if using webcamd via the RC script, is to disable HAL in /etc/rc.conf or to comment out the HAL autodetection section in webcamd's RC script.
Can you do a ktrace on webcamd, to figure out why it doesn't connect to hal?
I've never used ktrace before, so I had to read the man page. I hope I used it correctly. I started hal with "service hald start" then ran "ktrace -tcnisuw -i webcamd -N Logitech-Logitech-Dual-Action -M 0 -H" from the command line. But even though there are some /var/run/hald/dbus-xxxxxxxxxx files with the timestamp of when I started hal, I can't find in top or KDE's system monior any sign that hal is remaining resident after starting it. So maybe hal is starting and immediately exiting for some reason?
Created attachment 212515 [details]
This appears that it may just be a hald issue and not a webcamd issue. Hal is indeed crashing, so I opened a bug for hald crashing on startup. It's bug 244958.
Is hald installed in your system?
ps auxw | grep hal
I followed up on the HAL bug I filed. HAL is no longer crashing and I haven't been able to reproduce the crash. Since this turned out to be primarily an issue with HAL, maybe this should be closed. The only suggestion I would have is, if possible, implement either a fallback mechanism or maybe have a timeout period and emit an error message if webcamd is unable to connect to HAL. A fallback mechanism would probably result in just masking an issue if one were to occur and it not being discovered. At least if it failed and exited with something like "Unable to connect to HAL. Is HAL running?" it could provide enough information to a user to pinpoint the problem if HAL were to act up again.