id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
16377	qtwebengine-5.15.9	ken@…	ken@…	"The expected release date of paid-for qt-5.15.9 was March. It seems that the updates for qtwebengine were completed by 30th March, although the latest commit to merge chromium changes did not hit 5.15 until this week (merged by a bot).

Unusually, the build fixes patch from 5.15.8 all applies.

Even more unusually, one of the upstream patches for qtwebengine itself broke my build [https://code.qt.io/cgit/qt/qtwebengine.git/commit/?h=5.15.9&id=34b5b4b19c510aa6d701119d9c594a754bd21afc] - that adds one line,
{{{
contentMainParams.setup_signal_handlers = false;
}}}
with a comment ""We used to have this, but it got dropped at some point in an adaptions.""

In my build, that causes
{{{
/scratch/working/qtwebengine-5.15.9/src/core/web_engine_context.cpp:799:23: error: 'struct content::ContentMainParams' has no member named 'setup_signal_handlers'
  799 |     contentMainParams.setup_signal_handlers = false;
      |                       ^~~~~~~~~~~~~~~~~~~~~
}}}
and that is the ONLY reference to setup_signal_handlers that I can find (and nothing at all in full qt-5.15.2, nor in the modules for which I have pulled kf5 patches.

Looking at the bug it is intended to fix, [https://bugreports.qt.io/browse/QTBUG-99263] the bug was reported against 6.2 on macOS. I've seen a previous oddity in one of the kf5 patches re macOS (public 5.15.2 didn't seem to include what was being patched). Whatever, it apparently built in qt's own testing but it doesn't build for me, so I've dropped it.

There are 30 new CVEs since 5.15.8 - with the exception of picking up the expat fix ('Critical'), maximum severity seems to be High although some are not yet public, and at least one of the High ones has been reported to be actively exploited. 


"	enhancement	closed	normal	11.2	BOOK	git	medium	fixed