QGC Installation/Configuration Problems
This topic lists troubleshooting information related to running QGroundControl on the host computer (e.g. QGC setup and configuration issues).
Problems when using QGroundControl to interact with a vehicle are covered in: QGC/Vehicle Interaction Problems.
64-bit Windows: Audio in Unexpected Language
On Windows 64-bit machines QGroundControl may sometimes play audio/messages in a language that does not match the Text-to-speech setting in Control Panel > Speech (e.g. audio spoken in German on an English machine).
This can occur because 64-bit Windows only displays 64-bit voices, while QGroundControl is a 32-bit application (on Windows) and hence can only run 32-bit voices.
The solution is to set the desired 32-bit voice for your system:
- Run the control panel application: C:\Windows\SysWOW64\Speech\SpeechUX\sapi.cpl.
- Make your desired Voice selection and then click OK at the bottom of the dialog.
Additional information about the Windows speech APIs can be found here.
Windows: UI Rendering/Video Driver Issues
If you experience UI rendering issues or video driver crashes on Windows, this may be caused by "flaky" OpenGL drivers. QGroundControl provides 3 shortcuts that you can use to start QGroundControl in "safer" video modes (try these in order):
- QGroundControl: QGC uses OpenGL graphics drivers directly.
- GPU Compatibility Mode: QGC uses ANGLE drivers, which implement OpenGL on top of DirectX.
- GPU Safe Mode: QGC uses a software rasterizer for the UI (this is very slow).
Windows: Waiting For Vehicle Connection over WiFi
If QGroundControl sits forever Waiting For Vehicle Connection when trying to connect to the vehicle over Wifi, a possible cause is that IP traffic is being blocked by firewall software (e.g. Windows Defender, Norton, etc.).
The solution is to allow the QGroundControl app through the firewall.
If using Windows Defender:
- In the Start bar, enter/select: Firewall & Network Protection (System Settings).
- Scroll to and select the option: Allow an app through firewall.
- Select QGroundControl and change the Access selector to Allow.
Programs are listed in alphabetical order by description (not filename). You'll find QGC under O: Open source ground control app provided by QGroundControl dev team
Ubuntu: Video Streaming Fails (Missing Gstreamer)
On Ubuntu you must install Gstreamer components in order to see video streams. If these are not installed QGroundControl is unable to create the gstreamer nodes and fails with:
VideoReceiver::start() failed. Error with gst_element_factory_make(‘avdec_h264’)
The download/install instructions for Ubuntu include GStreamer setup information.
Ubuntu 18.04: Video Streaming Fails on Dual Video Adapter Systems
The version of GSteamer in Ubuntu 18.04 has a bug that prevents video displaying when using a VA API based decoder (i.e. vaapih264dec etc.) on systems that have both Intel and NVidia video display adapters.
More generally, while the problem is known to occur on Ubuntu 18.04 with Intel and NVidia VGAs, it might occur on any linux system and other types of (dual) VGAs.
The easiest way to get QGroundControl to work in this case is to start it using the following command line:
LIBVA_DRIVER_NAME=fakedriver ./QGroundControl) will this make the
Other alternatives are to disable one of the VGAs, uninstall VA API components, or upgrade to GStreamer 1.16 (there is no easy way to do this on Ubuntu 18.04 - please contribute a recipe if you find one!)
Ubuntu 16.04: GLIBC_2.27 not found
The pre-built AppImages for QGroundControl 4.0 (and later) can only run on Ubuntu 18.04 LTS (or later). They do not run on Ubuntu 16.04.
If you try you will get the error as shown:
$ ./QGroundControl.AppImage /tmp/.mount_i4hPuB/QGroundControl: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /tmp/.mount_i4hPuB/QGroundControl)
If you need to use Ubuntu 16.04 then one workaround is to build from source without the video libraries.