Qt 5.13.0 Known Issues: Difference between revisions
(Created page with "Category:Known Issues *Check that your system meets [http://doc-snapshots.qt.io/qt5-5.9/gettingstarted.html#platform-requirements Qt's requirements] *All open issues can b...") |
|||
| (11 intermediate revisions by 5 users not shown) | |||
| Line 2: | Line 2: | ||
*Check that your system meets [http://doc-snapshots.qt.io/qt5-5.9/gettingstarted.html#platform-requirements Qt's requirements] | *Check that your system meets [http://doc-snapshots.qt.io/qt5-5.9/gettingstarted.html#platform-requirements Qt's requirements] | ||
*All open issues can be found from Jira: https://bugreports.qt.io | *All open issues can be found from Jira: https://bugreports.qt.io | ||
**RTA findings here | **RTA findings [https://bugreports.qt.io/issues/?filter=20543 here] | ||
== OpenSSL == | |||
Qt 5.13.0 requires OpenSSL 1.1.1 version on Linux and Windows. Qt online installer provides as convenience both OpenSSL source code and pre-built binaries of the OpenSSL libraries used by Qt Network. However, the installer doesn't set up OpenSSL environment. User needs to define the library path and possible environment variables. OpenSSL libraries are not automatically deployed with applications that are built with Qt. If provided OpenSSL binaries are not suitable for your use case source code installation includes instructions on how to configure and build your own OpenSSL libraries. | |||
Import and export restrictions apply for some types of software, and for some parts of the world. Developers wishing to use SSL communication in their deployed applications should either ensure that their users have the appropriate libraries installed, or they should consult a suitably qualified legal professional to ensure that applications using the code from the OpenSSL project are correctly certified for import and export in relevant regions of the world. | |||
See more instructions from {{Issue|QTCREATORBUG-22587}} | |||
== All platforms == | == All platforms == | ||
* WebEngine cannot load PDFs with spaces in the url name, see {{Issue|QTBUG-76226}} | |||
==Windows== | ==Windows== | ||
* ActiveQt includes the debug library dependencies when building a release version of something using it, see {{Issue|QTBUG-76337}} | |||
* WebEngine 32 bit debug builds show crashes on some web pages. 32 bit release or 64 bit builds are not affected. | |||
==Linux== | ==Linux== | ||
* PDF viewing in Qt WebEngine using the Chromium extensions is disabled in the official packages, but works in self-compiled version as long as they are using clang or GCC 6 or higher. For details, see [https://bugreports.qt.io/browse/QTBUG-76329 QTBUG-76329]. | |||
==macOS== | ==macOS== | ||
==Android== | ==Android== | ||
[[Qt for Android known issues]] | |||
==iOS== | ==iOS== | ||
==UWP== | ==UWP== | ||
QTBUG-75620: WinRT: Fix crash in native socket engine during close | |||
==QNX== | ==QNX== | ||
Latest revision as of 11:02, 19 June 2019
- Check that your system meets Qt's requirements
- All open issues can be found from Jira: https://bugreports.qt.io
- RTA findings here
OpenSSL
Qt 5.13.0 requires OpenSSL 1.1.1 version on Linux and Windows. Qt online installer provides as convenience both OpenSSL source code and pre-built binaries of the OpenSSL libraries used by Qt Network. However, the installer doesn't set up OpenSSL environment. User needs to define the library path and possible environment variables. OpenSSL libraries are not automatically deployed with applications that are built with Qt. If provided OpenSSL binaries are not suitable for your use case source code installation includes instructions on how to configure and build your own OpenSSL libraries.
Import and export restrictions apply for some types of software, and for some parts of the world. Developers wishing to use SSL communication in their deployed applications should either ensure that their users have the appropriate libraries installed, or they should consult a suitably qualified legal professional to ensure that applications using the code from the OpenSSL project are correctly certified for import and export in relevant regions of the world.
See more instructions from QTCREATORBUG-22587
All platforms
- WebEngine cannot load PDFs with spaces in the url name, see QTBUG-76226
Windows
- ActiveQt includes the debug library dependencies when building a release version of something using it, see QTBUG-76337
- WebEngine 32 bit debug builds show crashes on some web pages. 32 bit release or 64 bit builds are not affected.
Linux
- PDF viewing in Qt WebEngine using the Chromium extensions is disabled in the official packages, but works in self-compiled version as long as they are using clang or GCC 6 or higher. For details, see QTBUG-76329.
macOS
Android
iOS
UWP
QTBUG-75620: WinRT: Fix crash in native socket engine during close