Bug #1238
closed
raspi2fb is not starting
100%
Description
raspi2fb is not always starting with PiCam.
There two known bugs in the init script called by PiCam:
${ECHO} "Starting logging: "should be
echo "Starting logging: "because "${ECHO} is not defined for raspi2fb (might be in /etc/init.d/functions but that isn't sourced by raspi2fb).
The other is that there is a space between #! and the shell path at the start of the script.
Even with those two fixes raspi2fb is not being started by picam, even though the logs say it is:
playerProcessor[player.c:230] INFO Starting raspi2fbd: /etc/init.d/raspi2fbd startNote that as long as raspi2fb starts the app runs fine. Also, there may be some issues with stopping raspi2fb. It appears to stop, but doesn't.
playerProcessor[player.c:246] INFO Stopping raspi2fbd: /etc/init.d/raspi2fbd stop
Updated by Hammel about 23 hours ago
- Description updated (diff)
I'm wondering if this is just a permissions problem. Picam needs to be privileged to run raspi2fb, I think.
Updated by Hammel about 23 hours ago
- Status changed from New to In Progress
- % Done changed from 0 to 50
Bingo. Adding picam to priv config fixes the problem.
Updated by Hammel about 20 hours ago
- % Done changed from 50 to 70
Updated the raspi2fbd script with the specified fixes.
Updated by Hammel about 20 hours ago
- % Done changed from 70 to 80
Picam opkg postinst already updates appmgr.priv. Not sure why it wasn't there before.
Need to reinstall picam and raspi2fb on pisentry and retest.
Updated by Hammel about 2 hours ago
- Status changed from In Progress to Closed
- % Done changed from 80 to 100
Verified a fresh build of PiSentry works as expected now.
All changes committed and pushed.
Closing issue.