qtdeclarative-opensource-src.git
2 months agouse qWaitForWindowExposed instead of qWaitForWindowActive
Dmitry Shachnev [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
use qWaitForWindowExposed instead of qWaitForWindowActive

Forwarded: no
Last-Update: 2019-04-21

The qWaitForWindowActive() function returns false when the test is
run inside Xvfb and there is no window manager.

Gbp-Pq: Name wait_for_window_exposed.patch

2 months agoMake sure that tests run with just compiled versions of tools
Sandro Knauß [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
Make sure that tests run with just compiled versions of tools

Origin: Debian
Last-Update: 2020-09-08

Last-Update: 2020-09-08
Gbp-Pq: Name fix_test_remove_qlibraryinfo.patch

2 months agoDisable all tests that fails with xvfb
Sandro Knauß [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
Disable all tests that fails with xvfb

Origin: Debian
Forwarded: not-needed - it is a limitation so far inside Debian
Last-Update: 2019-03-14

So far some tests need real OpenGL support

Gbp-Pq: Name disableopengltests.patch

2 months agorich text: limit size of text object
Debian Qt/KDE Maintainers [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
rich text: limit size of text object

Origin: upstream, https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=144ce34e846b3f73
 Backported to 5.15 by Dmitry Shachnev: validate allocation manually
 instead of using QImageIOHandler::allocateImage().
Last-Update: 2025-12-11

When we draw a text object, we need to store this in RAM
since the QTextObjectInterface is QPainter-based. This
could lead to over-allocation if the text object size
was set to be very large. We use the existing image IO
infrastructure for making sure allocations are within
reasonable (and configurable) limits.

Gbp-Pq: Name CVE-2025-12385-part2.patch

2 months agoincrease robustness of <img> tag in Text component
Debian Qt/KDE Maintainers [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
increase robustness of <img> tag in Text component

Origin: upstream, https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=4aaf9bf21f7cc69d
Last-Update: 2025-12-09

For Text.StyledText, there was no protection against <img> tags
with very large widths or heights. This could cause an application
to spend a very long time processing a layout and sometimes crash
if the size was too large.

We reuse the internal coord limit in QPainter as our maximum size
here, similar to what we do in Qt Svg for instance.

For Text.RichText, there were no issues in release builds, but in
debug builds, you could trigger an overflow assert when rounding
the number if it exceeded INT_MAX. For this, we simply cap the
width and height at INT_MAX.

Gbp-Pq: Name CVE-2025-12385.patch

2 months agoQML: fortify qmlExecuteDeferred some more
Debian Qt/KDE Maintainers [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
QML: fortify qmlExecuteDeferred some more

Origin: upstream, https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=f69b6f0940b178b4
Last-Update: 2024-11-07

Gbp-Pq: Name fortify_qmlexecutedeferred.patch

2 months agoQQuickItem: avoid emitting signals during destruction
Debian Qt/KDE Maintainers [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
QQuickItem: avoid emitting signals during destruction

Origin: upstream, https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=74873324bdf33997
Last-Update: 2023-02-26

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.

Gbp-Pq: Name qquickitem_no_signals_on_destruction.patch

2 months agomake tst_qmldiskcache::regenerateAfterChange() pass on big endian systems
Debian Qt/KDE Maintainers [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
make tst_qmldiskcache::regenerateAfterChange() pass on big endian systems

Origin: upstream, https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=dab0d62b655ce9a4
Last-Update: 2021-02-11

Gbp-Pq: Name tst_qmldiskcache_big_endian.patch

2 months agoqtdeclarative-opensource-src (5.15.17+dfsg-4) unstable; urgency=medium
Dmitry Shachnev [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
qtdeclarative-opensource-src (5.15.17+dfsg-4) unstable; urgency=medium

  * Backport upstream patches to fix CVE-2025-12385 (closes: #1122055).
  * Update symbols files from buildds’ logs.

[dgit import unpatched qtdeclarative-opensource-src 5.15.17+dfsg-4]

2 months agoImport qtdeclarative-opensource-src_5.15.17+dfsg-4.debian.tar.xz
Dmitry Shachnev [Thu, 11 Dec 2025 10:02:24 +0000 (13:02 +0300)]
Import qtdeclarative-opensource-src_5.15.17+dfsg-4.debian.tar.xz

[dgit import tarball qtdeclarative-opensource-src 5.15.17+dfsg-4 qtdeclarative-opensource-src_5.15.17+dfsg-4.debian.tar.xz]

8 months agoImport qtdeclarative-opensource-src_5.15.17+dfsg.orig.tar.xz
Dmitry Shachnev [Sat, 5 Jul 2025 09:43:04 +0000 (12:43 +0300)]
Import qtdeclarative-opensource-src_5.15.17+dfsg.orig.tar.xz

[dgit import orig qtdeclarative-opensource-src_5.15.17+dfsg.orig.tar.xz]