The problem apparently is triggered by a change in Qt 5.12.0 though, so it's not necessarily a bug in the intel driver... *** This bug has been marked as a duplicate of bug 1120090 ***