| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| gcc_11.patch | build fixes for GCC 11 | no | upstream, https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=eb6525f126f680f9 | 2022-11-05 | ||
| tst_qmldiskcache_big_endian.patch | make tst_qmldiskcache::regenerateAfterChange() pass on big endian systems | no | upstream, https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=dab0d62b655ce9a4 | 2021-02-11 | ||
| support_apos_in_styled_text.patch | Support ' in styled text and document it This ensures that some translations really look ok. | Albert Astals Cid | not-needed | https://invent.kde.org/qt/qt/qtdeclarative/-/merge_requests/3/diffs | ||
| fix_sweep_step.patch | fix sweep step for tainted QObject JavaScript wrappers Currently, whenever the garbage collector runs, it will destroy all valid tainted wrappers. . Only null or undefined wrappers will be preserved in the m_multiplyWrappedQObjects map. . It seems like "!" was overlooked in 3b5d37ce3841c4bfdf1c629d33f0e33b881b47fb. Prior to that change, it was "!it.value()->markBit()", so calling erase() in the then branch did make sense. But with "!it.value().isNullOrUndefined()", erase() will be called for every valid wrapper, which is the opposite what we want. |
no | upstream, https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=e6b2f88d892dcf39 | 2022-02-13 | ||
| qquickitem_no_signals_on_destruction.patch | QQuickItem: avoid emitting signals during destruction If a QQuickItem is in the QQuickItem destructor, then it is both unsafe and unnecessary to emit property change notifications. Connected code can no longer rely on the state of the emitting object - if it was originally a subclass of QQuickItem, then those subclass destructors will already have run. And the QQuickItem destructor will also have partially run, leaving the object in an undefined state. . Add a flag that we set to true at the top of ~QQuickItem, and don't emit visibleChildrenChanged, parentChanged, visibleChanged, and childrenChanged for items that are partially destroyed already. . [ChangeLog][Qt Quick][QQuickItem] QQuickItem no longer emits change notifications for the parent, children, visible, and visibleChildren properties while it is being destroyed. |
no | upstream, https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=74873324bdf33997 | 2023-02-26 | ||
| disableopengltests.patch | Disable all tests that fails with xvfb So far some tests need real OpenGL support | Sandro Knau <bugs@sandroknauss.de> | not-needed | Debian | 2019-03-14 | |
| fix_test_remove_qlibraryinfo.patch | Make sure that tests run with just compiled versions of tools | Sandro Knau <bugs@sandroknauss.de> | no | Debian | 2020-09-08 | |
| wait_for_window_exposed.patch | use qWaitForWindowExposed instead of qWaitForWindowActive The qWaitForWindowActive() function returns false when the test is run inside Xvfb and there is no window manager. |
Dmitry Shachnev <mitya57@debian.org> | no | 2019-04-21 | ||
| remove_youtube_iframe.patch | replace YouTube iframe with YouTube link | Dmitry Shachnev <mitya57@debian.org> | not-needed | 2019-12-19 | ||
| riscv64-latomic.patch | link with -latomic on riscv64 | Aurelien Jarno <aurel32@debian.org> | no | 2020-01-01 | ||
| python3.patch | make qtdeclarative build with Python 3 | Antonio Larrosa <alarrosa@suse.com> | invalid | OpenSUSE, https://build.opensuse.org/package/view_file/KDE:Qt:5.12/libqt5-qtdeclarative/qtdeclarative-switch-to-python3.patch | 2020-01-01 |