Hello Marius, or anyone else affected, Accepted qtdeclarative-opensource-src into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qtdeclarative-opensource- src/5.15.13+dfsg-1ubuntu0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: qtdeclarative-opensource-src (Ubuntu Noble) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/2111216 Title: Qt V4 JIT engine generates bad JIT code Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Noble: Fix Committed Bug description: [ Impact ] We're encountering a critical issue in Qt 5.15.13 as shipped in Ubuntu 24.04 (Noble). The Qt V4 JIT engine occasionally generates invalid machine code, resulting in crashes at runtime. This issue is tracked upstream as https://bugreports.qt.io/browse/QTBUG-111935, and was fixed in Qt 5.15.14. Symptoms: * Application crashes with segmentation faults or illegal instruction errors when executing certain JavaScript in QML (GC). * The issue appears to stem from bad register allocation or incorrect code paths during JIT compilation. This affects users using Lomiri (and plasma) on arm64 (maybe others) devices. It causes random crashes in normal day to day use, 100% with QV4_MM_AGGRESSIVE_GC=1, never with QV4_FORCE_INTERPRETER=1. [ Test Plan ] * Start plasmashell or lomiri with set QV4_MM_AGGRESSIVE_GC=1. [ Where problems could occur ] The fix touches the JIT interpreter code, so potential problems would occur there. However, we run upstream test suite during build, so it should catch any potential regressions. [ Other Info ] Upstream commit that resolves the issue: https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=3bd18f41cfb0f3da65eecf216e49a9bb6bda71a6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/2111216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
