Debugging License Issues on Linux - Cheat Sheet / Manual


this is just a short “manual” or reference on how to resolve license issues with CVB on Ubuntu/Linux systems.

This post assumes you do NOT use the LicenseManager (this is our UI tool for licenses), because your system does not have a desktop environment.

NOTE for an explanation for licenses on Windows or the LicenseManager, open:

Typically a missing license will result in watermarks.

I. Ensure the following services are running

  • codemeter (this service does NOT exist on armhf/armv7 and arm64/aarch64 systems)
  • cvmgmtd (CVB Management Service)
  • siGevSvc (if you have not GigE Vision cameras, you can ignore this)

Use “sudo service insert-service-name status” to determine the status. And use “sudo service insert-service-name restart”, to start/restart if needed.

An active service will print “active (running)”. Anything else might suggest an issue.

II. Add your CameraSuite licenses

(Again this can also be done via the LicenseManager tool.)
We simply append our license key to /opt/cvb/camerasuite.lic

  • sudo touch /opt/cvb/camerasuite.lic
  • sudo chmod a+rw /opt/cvb/camerasuite.lic
  • printf “AAAA-BBBB-CCCC-DDDD-EEEE-FFFF-GGGG\n” >> /opt/cvb/camerasuite.lic

Camerasuite license MUST match the corresponding camera, i.e. it’s a new license for each camera.

This is a Camerasuite license, the key “KFTJ-D…” is the camerasuite license.

III. Check via API for license

It is recommended to check for license at the start of your application. This way you have feedback if your license works ( and for some licenses (U3V) the check is not done during opening your device).

For C++ use Cvb::Utilities::SystemInfo::WaitForLicense(…)