Known Issues

This section lists known issues in Qt Creator version 8.0.1. The development team is aware of them, and therefore, you do not need to report them as bugs.

For a list of fixed issues and added features, see the changelog file in the qtcreator\dist folder or the Qt Project Bug Tracker.

General Issues

• If you change the Input Languages in Windows, Qt Creator might not respond for 30 seconds. This is a known issue in the Advanced Text Service of Microsoft Windows.
• Qt Creator uses SQLite for storing some of its settings. SQLite is known to have problems with certain NFS servers (most notably the nfs-user-server 2.2beta), since they can lock up the application when it tries to lock the database. If your home directory is on an NFS share and you encounter this issue, one option would be to switch to the nfs-kernel-server, or create a symlink so that the settings are stored locally.
• The Okteta KDE custom widget plugin might be installed as part of some Linux distributions. It can cause Qt Designer to crash. For more information, see:
  • Ubuntu bug 662005
  • QTBUG-12025

  To resolve the issue, enter the following command to remove the package:

   sudo apt-get remove okteta
  

  Or delete the following file: /usr/lib/kde4/plugins/designer/oktetadesignerplugin.so.

Editing Issues

• Code completion does not support typedefs for nested classes.

Projects Issues

• Paths or file names containing spaces or special characters (such as colons, dollar signs, and hash marks) may cause problems. This is because some of the tools Qt Creator uses in the background have restrictions on the characters allowed in file and directory names. To be on the safe side, we recommend creating projects and project items with names consisting of plain characters, numbers, underscores, and hyphens.
• If error messages displayed in Compile Output contain paths where slashes are missing (for example, C:QtSDK), check your PATH variable. For more information, see Troubleshooting MinGW Compilation Errors.

Debugging Issues

• When debugging executables created by the GNU Compiler version 4.5.0 (all platforms), some data types will not be displayed in the Locals and Expressions views due to missing debug information.
• GDB on Windows may not work if the 'Embassy ^® Security Center' software by 'Wave ^® Systems' is installed and active (causing crashes in vxvault.dll)).
• GDB may take long to load debugging symbols, especially from large libraries.
• Setting breakpoints in code that is compiled into the binary more than once does not work.
• Setting breakpoints in files that do not have unique absolute paths may fail. For example, remounting parts of a file system using the --bind mount option.
• Setting breakpoints in files will fail when using LLDB if the file path contains symbolic links.
• A regression in GCC 4.5.0 causes return value optimization to produce inaccurate debug info that GCC applies also to non-optimized builds. For more information, see GCC Bugzilla - Bug 44731.