Qt 5.3.1 Known Issues: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
=Known Issues – Qt 5.3.1=
[[Category:Release::Known Issues]]<br />h1. Known Issues - Qt 5.3.1


==All platforms==
== All platforms ==


* Check that your system meets [http://doc-snapshot.qt.io/qt5-5.3/gettingstarted.html#platform-requirements Qt’s requirements] ''[doc-snapshot.qt.io]''
* Check that your system meets &quot;Qt's requirements&amp;quot;:http://doc-snapshot.qt.io/qt5-5.3/gettingstarted.html#platform-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


* Installation over the existing installation not supported
* Installation over the existing installation not supported
** <span class="caps">QTIFW</span>-278: <span class="caps">SDK</span> 5.1.0 rc1 : installation over existing installation fails
** QTIFW-278: SDK 5.1.0 rc1 : installation over existing installation fails


* Examples in Qt Creator Welcome mode is empty
* Examples in Qt Creator Welcome mode is empty
** Workaround: Start Qt Creator with clean settings (e.g. for temporary testing: ‘-settingspath /some/temp/dir’
** Workaround: Start Qt Creator with clean settings (e.g. for temporary testing: '<s>settingspath /some/temp/dir'
<br />* Late change file updates missing from official packages<br />'''''' Up-to-date change files here: https://wiki.qt.io/Change-files-in-Qt-5.3.1
<br />* Qt Creator still shows 5.3.0 as Qt / Kit version number, although I updated<br />'''''' QTBUG-39749: Qt Creator caches the Qt / Kit version names in your profile. Workaround is to nuke your local Qt Creator settings.
<br />h2. Linux
<br />* QTBUG-35516: example directory in binary package has wrong permissions (creating problems for global installations)<br />'''''' Workaround: Fix permissions with 'chmod g+rx,o+rx 5.2.0/gcc_64/examples'<br />* QTBUG-39897: Packaged libQtWebKit fails to load: conflict between (system) libxml2 and shipped libicu<br />'''''' This can show up e.g. in crashes when trying to open Qt Creator's Help, Widget Designer, or Qt Assistant.
<br />h2. Windows
<br />* if you want to install a Qt for Visual Studio be sure you have the related Visual Studio installed<br />* Qt Creator does not support Windows XP.<br />'''''' Workaround: Disable 'Welcome', 'QmlProfiler', QmlDesigner' plugins
<br />* Qt Creator does require a working DirectX/DirectDraw backend<br />'''''' Enable Accelerated 3D support if you run Windows in e.g. VirtualBox, VMWare
<br />* QTBUG-32864: WMF plugin fails to load on Windows Vista (no service found for</s> &quot;org.qt-project.qt.mediaplayer&amp;quot;)
** Workaround: If you target Windows Vista, rebuild the plugin (qtmultimedia/src/plugins/wmf) using the Windows Vista SDK.


* Late change file updates missing from official packages
* QTBUG-33788: Widgets in QGraphicsView via QGraphicsProxyWidget can't receive QTabletEvent
** Up-to-date change files here: https://wiki.qt.io/Change-files-in-Qt-5.3.1


* Qt Creator still shows 5.3.0 as Qt / Kit version number, although I updated
== WinRT / Windows Phone ==
** <span class="caps">QTBUG</span>-39749: Qt Creator caches the Qt / Kit version names in your profile. Workaround is to nuke your local Qt Creator settings.
 
==Linux==
 
* <span class="caps">QTBUG</span>-35516: example directory in binary package has wrong permissions (creating problems for global installations)
** Workaround: Fix permissions with ‘chmod g+rx,o+rx 5.2.0/gcc_64/examples’
* <span class="caps">QTBUG</span>-39897: Packaged libQtWebKit fails to load: conflict between (system) libxml2 and shipped libicu
** This can show up e.g. in crashes when trying to open Qt Creator’s Help, Widget Designer, or Qt Assistant.
 
==Windows==
 
* if you want to install a Qt for Visual Studio be sure you have the related Visual Studio installed
* Qt Creator does not support Windows XP.
** Workaround: Disable ‘Welcome’, ‘QmlProfiler’, QmlDesigner’ plugins
 
* Qt Creator does require a working DirectX/DirectDraw backend
** Enable Accelerated 3D support if you run Windows in e.g. VirtualBox, <span class="caps">VMW</span>are
 
* <span class="caps">QTBUG</span>-32864: <span class="caps">WMF</span> plugin fails to load on Windows Vista (no service found for – “org.qt-project.qt.mediaplayer”)
** Workaround: If you target Windows Vista, rebuild the plugin (qtmultimedia/src/plugins/wmf) using the Windows Vista <span class="caps">SDK</span>.
 
* <span class="caps">QTBUG</span>-33788: Widgets in QGraphicsView via QGraphicsProxyWidget can’t receive QTabletEvent
 
==WinRT / Windows Phone==


* If you want to install Qt for Windows RT or Phone, please have also the according Visual Studio installed (Visual Studio for Windows, Visual Studio for Windows Phone)
* If you want to install Qt for Windows RT or Phone, please have also the according Visual Studio installed (Visual Studio for Windows, Visual Studio for Windows Phone)
Line 47: Line 31:
* Automatic kit registration wrongly sets up WinRT target as local desktop target. This is related to the WinRT plugin not enabled by default. Please open Help-&gt;About Plugins, enable WinRT and restart Qt Creator
* Automatic kit registration wrongly sets up WinRT target as local desktop target. This is related to the WinRT plugin not enabled by default. Please open Help-&gt;About Plugins, enable WinRT and restart Qt Creator


==Mac OS X==
== Mac OS X ==


* <span class="caps">QTBUG</span>-31724: can’t debug into qt libs on Mac (it hasn’t worked since 5.0.0)
* QTBUG-31724: can’t debug into qt libs on Mac (it hasn’t worked since 5.0.0)
** Workaround: Compile Qt on your own (configure -developer-build provides both release and debug libs)
** Workaround: Compile Qt on your own (configure -developer-build provides both release and debug libs)


* <span class="caps">QTBUG</span>-35211: Apps using Qt WebKit 2.0 are not deployable on Mac OS X (QtWebProcess fails to deploy/start)
* QTBUG-35211: Apps using Qt WebKit 2.0 are not deployable on Mac OS X (QtWebProcess fails to deploy/start)
 
* <span class="caps">QTBUG</span>-35317: Qt Quick1 apps that use Qt WebKit 1.0 fail to deploy on Mac OS X
 
* <span class="caps">QTBUG</span>-35506: Qt Quick Controls applications launched using qmlscene might not display the menubar until they lose and regain focus


* <span class="caps">QTBUG</span>-38835: <span class="caps">REG</span>: QtQuick.Dialogs.FontDialog doesn’t display on iOS and OS X. workaround: [https://codereview.qt.io/85057 FontDialog: restore the font and weight list on iOS and <span class="caps">OSX</span>] ''[codereview.qt.io]'' . Will be fixed in stable: [https://codereview.qt.io/85410 Fix interaction of garbage collector with JS objects during <span class="caps">QML</span> type instantiation] ''[codereview.qt.io]''
* QTBUG-35317: Qt Quick1 apps that use Qt WebKit 1.0 fail to deploy on Mac OS X  


==Android==
* QTBUG-35506: Qt Quick Controls applications launched using qmlscene might not display the menubar until they lose and regain focus


See “[[Qt for Android known issues]]“
* QTBUG-38835: REG: QtQuick.Dialogs.FontDialog doesn't display on iOS and OS X. workaround: &quot;FontDialog: restore the font and weight list on iOS and OSX&amp;quot;:https://codereview.qt.io/85057 . Will be fixed in stable: &quot;Fix interaction of garbage collector with JS objects during QML type instantiation&amp;quot;:https://codereview.qt.io/85410


==iOS==
== Android ==


See “[[Qt for iOS known issues]]“
See &quot;[[Qt_for_Android_known_issues|Qt for Android known issues]]&quot;


==BlackBerry 10==
== iOS ==


See “[[Qt5 Status on BlackBerry10|Qt5 Status on BlackBerry 10]]“
See &quot;[[Qt_for_iOS_known_issues|Qt for iOS known issues]]&quot;


==<span class="caps">QNX</span>==
== BlackBerry 10 ==


See “[[Qt Status on QNX|Qt Status on <span class="caps">QNX</span>]]“
See &quot;[[Qt5_Status_on_BlackBerry10 | Qt5 Status on BlackBerry 10]]&quot;


===Categories:===
== QNX ==


* [[:Category:Release|Release]]
See &quot;[[Qt_Status_on_QNX | Qt Status on QNX ]]&quot;
** [[:Category:Release::Known-Issues|Known Issues]]

Revision as of 08:56, 24 February 2015


h1. Known Issues - Qt 5.3.1

All platforms

  • Installation over the existing installation not supported
    • QTIFW-278: SDK 5.1.0 rc1 : installation over existing installation fails
  • Examples in Qt Creator Welcome mode is empty
    • Workaround: Start Qt Creator with clean settings (e.g. for temporary testing: 'settingspath /some/temp/dir'


* Late change file updates missing from official packages
' Up-to-date change files here: https://wiki.qt.io/Change-files-in-Qt-5.3.1
* Qt Creator still shows 5.3.0 as Qt / Kit version number, although I updated
' QTBUG-39749: Qt Creator caches the Qt / Kit version names in your profile. Workaround is to nuke your local Qt Creator settings.
h2. Linux
* QTBUG-35516: example directory in binary package has wrong permissions (creating problems for global installations)
' Workaround: Fix permissions with 'chmod g+rx,o+rx 5.2.0/gcc_64/examples'
* QTBUG-39897: Packaged libQtWebKit fails to load: conflict between (system) libxml2 and shipped libicu
' This can show up e.g. in crashes when trying to open Qt Creator's Help, Widget Designer, or Qt Assistant.
h2. Windows
* if you want to install a Qt for Visual Studio be sure you have the related Visual Studio installed
* Qt Creator does not support Windows XP.
' Workaround: Disable 'Welcome', 'QmlProfiler', QmlDesigner' plugins
* Qt Creator does require a working DirectX/DirectDraw backend
' Enable Accelerated 3D support if you run Windows in e.g. VirtualBox, VMWare
* QTBUG-32864: WMF plugin fails to load on Windows Vista (no service found for "org.qt-project.qt.mediaplayer&quot;)

    • Workaround: If you target Windows Vista, rebuild the plugin (qtmultimedia/src/plugins/wmf) using the Windows Vista SDK.
  • QTBUG-33788: Widgets in QGraphicsView via QGraphicsProxyWidget can't receive QTabletEvent

WinRT / Windows Phone

  • If you want to install Qt for Windows RT or Phone, please have also the according Visual Studio installed (Visual Studio for Windows, Visual Studio for Windows Phone)
  • Note that not all mobile related modules are supported (e.g. Geopositioning, bluetooth, etc)
  • Even though Qt Cloud Services are part of the package, they are not supported yet.
  • Qt Quick Controls might have some wrong behaviors.
  • Automatic kit registration wrongly sets up WinRT target as local desktop target. This is related to the WinRT plugin not enabled by default. Please open Help->About Plugins, enable WinRT and restart Qt Creator

Mac OS X

  • QTBUG-31724: can’t debug into qt libs on Mac (it hasn’t worked since 5.0.0)
    • Workaround: Compile Qt on your own (configure -developer-build provides both release and debug libs)
  • QTBUG-35211: Apps using Qt WebKit 2.0 are not deployable on Mac OS X (QtWebProcess fails to deploy/start)
  • QTBUG-35317: Qt Quick1 apps that use Qt WebKit 1.0 fail to deploy on Mac OS X
  • QTBUG-35506: Qt Quick Controls applications launched using qmlscene might not display the menubar until they lose and regain focus
  • QTBUG-38835: REG: QtQuick.Dialogs.FontDialog doesn't display on iOS and OS X. workaround: "FontDialog: restore the font and weight list on iOS and OSX&quot;:https://codereview.qt.io/85057 . Will be fixed in stable: "Fix interaction of garbage collector with JS objects during QML type instantiation&quot;:https://codereview.qt.io/85410

Android

See "Qt for Android known issues"

iOS

See "Qt for iOS known issues"

BlackBerry 10

See " Qt5 Status on BlackBerry 10"

QNX

See " Qt Status on QNX "

Retrieved from "https://wiki.qt.io/index.php?title=Qt_5.3.1_Known_Issues&oldid=4062"