Dear CVB team,
I’m facing an issue related to system startup and make my application fully autonomous. For now the application is defined as a service that waits for network-online.target and cvmgmt.service to starts but it fails to connect to the camera (complaining about no accessible camera) until I login as a graphical user. We are able to connect the system and watch this through an SSH connection.
During this test the same user opens a distant SSH session to see service logs then it goes to the machine and logs in a graphical session. Before the graphical login service fails/waits/restarts as defined in the systemclt service definition and as soon as the graphical session starts the service gains an access to the camera and is able to operate as desired.
The current awful workaround is to enable autologin which means huge security breach. Do you have a prettier solution to make the camera accessible without any graphical session running?