Some more tidbits. We ran and tested this in California just fine. When the laptop arrived in Sabah, we discovered that the permissions on the AppImage file no longer included the precious ‘x’ for executable. What kind of service in Linux could cause permissions to change like that? That remains unclear. We chmod’d and found that the app seg faults. We downloaded it again and diff’d. No change to the executable AppImage file. OK, worked in California, whatever.
Our Malaysian contact reported similar issues due to regional issues, so we checked out AppArmor and found this post:
We disable AppArmor for QGroundControl, but no joy. Then we found other cases where QGroundControl wouldn’t work with Wayland.
Even though it was working in California, we tried switching to X11 to see if that would work. No. We haven’t tried the other fixes in the above ticket yet, but will.
Has anyone else had troubles caused by changing regions? Thanks. Until we get this sorted, our project is going nowhere.
Alternatively, Cockpit is a great alternative to QGC as it can be installed on the ROV, so no setup on your control computer is required! It is also possible to run as a standalone application on Mac, Windows and Linux.
We’re generally moving away from using QGround Control completely, with Cockpit handling GCS and BlueOS handling vehicle setup of sensors…
Thank you again Tony. Did not know about Cockpit. Oh, and our version of QGroundControl is what we downloaded from here yesterday. It may give us the version to confirm before it segfaults, we’ll see. If your advice is to use Cockpit, then we’ll try it. Right now our team in Semporna is on standby, as is the maiden voyage off the BlueBoat carrying the bomb fishing sensor.