Tuukka Turunen

Qt 5.4.1 Released

Published Tuesday February 24th, 2015
36 Comments on Qt 5.4.1 Released
Posted in Releases

Today we have released Qt 5.4.1, the first patch update to Qt 5.4. In addition to improvements and fixes to Qt functionality it also packs new Qt Creator 3.3.1.

Qt 5.4.0 released in December introduced many features such as our new Chromium-based Qt WebEngine, WinRT support (including Windows Phone), and several Graphics improvements. With Qt 5.4.1 we are providing a good set of bug fixes and enhancements – thanks to all the feedback and reports we’ve received.

Qt 5.4.1 restores binary compatibility for Qt 5.3.2 (and the Qt 5 series) on Windows. Unfortunately Qt 5.4.0 broke binary compatibility on Windows when using MSVC 2012 or MSVC 2013, which is now fixed in Qt 5.4.1, and thus it maintains backward and forward compatibility with the Qt 5 series (except for Qt 5.4.0). Qt 5.4.1 also fixes many of the known issues of Qt 5.4.0, including building Qt on Linux without dbus (QTBUG-43205). Starting with Qt 5.4.1, QtDBus is enabled for all builds.

Other important fixes in Qt 5.4.1 include enabling JIT by default in the Qt Quick Engine (QTBUG-43171), a couple of critical fixes to OpenGL (QTBUG-43178 and QTBUG-43318), and fixes to Mac binaries (QTBUG-42594, QTBUG-43100). Qt 5.4.1 also provides a large number of improvements to WinRT (for example QTBUG-41769, QTBUG-43862, and QTBUG-44196), and adds support for Windows 10 Technical Preview (QTBUG-43413).

The device creation reference stacks for embedded Linux and embedded Android have also been updated to use Qt 5.4.1. There are some improvements in functionality, for example better support for compiling projects using embedded Linux toolchains and having add-on modules built into the image included in the generated Qt Creator custom Kit.

The full list of important changes can be found from the change files for each module.

The packages of Qt 5.4.1 also include new Qt Creator 3.3.1. See the blog post about Qt Creator 3.3.1 for the main improvements.

If you are using online installer, Qt 5.4.1 and Creator 3.3.1 can be updated using the maintenance tool. Offline packages are found from the Qt Account (for Enterprise users) and from the Download page (for Community users).

Join the live webinar

Please join us for a live webinar on Wednesday, 25 February where we will present an overview of Qt 5.4. We’ve spent countless hours ensuring that Qt 5.4 is our best release yet, and we can’t wait to show you what we’ve done! A copy of the recording will be sent to all webinar registrants, so please feel free to register even if you can’t attend due to limited live seating. Register now!

Do you like this? Share it
Share on LinkedInGoogle+Share on FacebookTweet about this on Twitter

Posted in Releases


Robert says:

Many issues have been fixed.

Unfortunately, many P2+P3 issues still left for iOS and Android-5.

I’d vote for higher quality and stability, particularly for these recently developed platforms, even on expense of more features.

Waiting for more stability in the next 5.4.2
Thank u once more!

Robert says:

Qt widgets on iOS are so memory effective that they are great for memory-consuming apps.

Please, do not forget widgets!

Adrian Gabureanu says:

1) I’m pretty much in favour of what you are saying. Furthermore I think there should be a focus on those issues that impact retention and monetization. For example, because of QTBUG-39712 and other similar bugs, on some devices, after each interstitial ad shown, the app crashed, went black or simply remained stuck. I see some of those issues were solved in Qt 5.4.1. Some were left for 5.4.2 as 5.4.1 was already late.

2) On WinRT I really don’t see how I could monetize my Qt apps. Should I use ads ? But does Qt allow integration of AdMob ads? In-app purchases ? It’s easier said than done. The C++ code for in-app purchases on WinRT is nothing like the C++ code Qt developers are used to. The fact that I can’t monetize, yet, discourages me from moving my Qt apps to WinRT.

3) How about sounds on WinRT – QTBUG-43664 ? Sounds make less than 1% of the source code, but they can accompany the user in more than 99% of the time he spends in an app.

Artem says:

It would be good to see some statement on Android-iOS priorities in general. At the moment mobile GUI-related and platform services integration-related efforts progress.. quite differently in Android and iOS.

It’s alright if Qt’s focus stays more on building devices and maybe on porting existing enterprise Qt apps to mobiles “somehow” rather than on building 95-100% native looking consumer apps. It would be good to hear about the priorities explicitly still.

@Artem: You are right that the ports to Android, iOS and WinRT have been progressing with different pace. We got a great heads-up in Android based on the work already done in the Necessitas project by BogDan and others. iOS started at the same time, but we started from scratch – only some parts can be shared from the work we do with Mac OS X. WinRT was the last one to start, but it is now catching up. We are getting closer in feature parity with each minor release of Qt – and continue to fix bugs in all of these with every patch release. So even though device creation is clearly the fastest growing domain, we do continue to support also the desktop and mobile platforms with Qt.

qq says:

I use qt for android and ios( mac version).
Does qt widget support wifi for android and ios.There are no example or document about wifi. I try to connect a wifi storage by my code using QTcpSocket. But it fail~

Artem says:

So the answer is “we’ll imporve something step by step”, right, Tuukka?

I was thinking more in lines of “yes, our target is to make creating 99-100% native looking iOS apps possible, yet it’s mid priority for now as is likely to be reached no earlier than 2016”

or maybe “It’s one of our top targets, we’ll do it ASAP”

or maybe “yes, we care of 95-100% Qt working well in mobiles, but exactly UI-wise, we are fine if it looks just somewhat native, prefer going pure QML way and will just update styles ones in a while”.

Robin Lobel says:

Congrats, the qtbase changelog is massive !

Malek Khlif says:

Gooooooooooooooooooooooooooooooooooooooooooooooooooooood I love Qt and Qt Creator <3

Volker SchK says:

With 5.4.1 (Creator 3.31) it seems to be impossible for me to run the Quick designer
What ever I do, with prev. projects or new ones on Win and Linux I always get the error:

“QT emulation Layer crashed (1:0)”

Anyone else with same issues?

espsousa says:

I’m getting the same :(…

Alexei says:

Me too.

JasonWong says:

Me too

Ariel says:

Yes, it is common, please report or comment here im trying to get some attention on them. I can get those errors in more than 40 computers making the QtC Designer close to useless.

Can you please vote or comment here?


aportale says:

This is bad, sorry for releasing it in such broken state, especially in a patch release. This crash happens in the community edition, apparently we just tested the commercial edition (where the issue does not occur).
Anyway, there is a workaround. In the Options dialog go to “Qt Quick / Qt Quick Designer / QML Emulation Layer” and disable the checkbox “Always use the QML emulation layer prived by Qt Creator” (screenshot). That will cause a rebuild of the emulation layer with the used Qt version in the current project. That layer does not crash. This workaround does however only work with Desktop Kits.

espsousa says:

Thank you, that workaround seems to solve it.

Chris Bruner says:

Work around didn’t fix for me. 🙁
I did a fresh maintenance update today (25th feb).

Thorin says:

What is the difference between community edition and the commercial one?
Why has only the community edition this bug if they are identical?

@Thorin: They are not identical. Qt Quick Designer, just like Profiler and some other tools provides more functionality in the paid version.

Thorin says:

What is the difference between community edition and the commercial one?
Why has only the community edition this bug if they are identical?

Really curious

cyoung says:

I just downloaded and installed the Community edition today (2/25). I tried the workaround above, and it still crashes!!!

Thomas Hartmann says:

Can you add your exact platform/environment as a comment to this bug report:


Using the workaround mentioned above we currently cannot reproduce any crash.

RealNC says:

Yey! The fonts on Linux are now actually readable!

At last, after many years, I can now update from Qt 4 and an outdated Creator to Qt 5.

But that issue take waaay too long to fix though. Actual years of an unusable Qt 5 on many Linux systems, without anyone from the Qt team trying to investigate the issue, even though users were volunteering to test out any debugging patches. At last it’s fixed, finally.

Andrey says:

Really? Man, something wrong with those fonts.


RealNC says:

They only look like that with the new release. Up to 5.4.0, they looked washed out, almost going transparent on a white background. Qt 4:


Qt 5:


It’s only with 5.4.1 that this issue was corrected.

Finally, in 2015, I can jump into the Qt 5 train 😛

jiangcaiyang says:

Congratulations on Qt release!
These days I’ve dive into Qt on mobile devices, thanks efforts by Qt developers, WinRT’s support will be more robust. I can’t wait downloading the latest version!

lynic says:

The WinPhone support is pretty stable. But WinRT (both arm and x86/x64) is not useable at the moment (arm graphics are broken on many devices, x86/x64 on many configurations). Its probably a problem with angle.

Alex says:

Dang, my 3 months old critical bug on Mac OS X is still not fixed 🙁
This means I still must build the Mac OS X version of my software with Qt 4, which, in turn, means users will get the “developer cannot be verified” message on OS X 10.10…


Dyami Caliri says:

You should really consider using QOpenGLWidget (since this issue happens with QGLWidget). It had some performance issues in 5.4.0 that are fixed in 5.4.1. We are very happy with it for our commercial application.

Alex says:

For one, while in my project the error occurs due to QGLWidget, the error itself is triggered by any native widget. So QOpenGLWidget might be a workaround, but it’s not a fix.
The problem with QOpenGLWidget is that the only way it can be non-native is for it to use the framebuffer, which is inherently slow. I used to use framebuffer in my project, but had to drop eventually due to performance issues.

Edward says:

Would this latest update prevent all of the Build menu items from being enabled (grayed out)? Projects can’t be built or .Exe files created. A fresh install from today.

Ville Lukka says:

Great work, congratulations!

On web things in Qt, I’m a bit buzzled.
1) Webkit is done and shall fade away.
2) Webengine (blink) is there to replace it, although not in api wise.
3) Webengine is not on mobile platforms, there is this WebView (the same name as in Webkit, but NOT the same).

The problem: http://doc.qt.io/qt-5/qtwebview-index.html it says: “is currently supported on the following platforms: Android and iOS.” How do we enable this? Or is it that it is supported only on commercial licenses? Because if it is, then it should be stated somewhere (or everywhere) explicitly, and also in the examples: http://doc.qt.io/qt-5/qtwebview-minibrowser-example.html

It is also a bit confusing, that WebView is part of webengine module, when the import statement in qml is different. Perhaps it makes perfect sense in development side of Qt.

So on document wise there could be done more to clarify things. What works in community edition and of course in commercials.

@Ville: WebView is available also for open-source users. It is a separate component to select in the installer.

yxb says:

great job!
which is pre-build for ‘-opengl dynimic’ version? is Mingw support this? thanks.

Commenting closed.

Get started today with Qt Download now