Engine 6.11.2-6

QtWebEngine 6.11.2 with Omaweb's patch series applied, for Linux x86_64 and aarch64.

This is the engine Omaweb runs on, and it is a modified QtWebEngine. It installs into /usr/lib/omaweb and does not replace the distribution's qt6-webengine, so every other Qt application on the machine keeps the engine it had.

What changed since engine-6.11.2-5. The Qt release and the Chromium it carries are the same: QtWebEngine 6.11.2 on Chromium 140.0.7339.225. No security fix comes with this release.

• An extension that creates an offscreen document no longer crashes the browser (patch 0019, Omaweb's #646). Bitwarden makes one, for example to clear the clipboard after a copy, and every time it did, the engine read a null delegate in RenderWidgetHostViewQt::Hide(). Qt's own 6.11.2 crashes the same way: reported as QTBUG-151304, with the fix on Gerrit as 778807.
• x86_64 is built against Qt 6.12.0, which Arch now ships, and requires qt6-base and qt6-declarative 6.12.0 or newer, with no upper bound (Omaweb's #660). aarch64 is built against Qt 6.11.2 and keeps its Qt dependencies unversioned, because Arch Linux ARM still ships 6.11.2.
• Patch 0020 is Qt's own change c9300848e28e (QTBUG-147006), which lets the engine's tests build against Qt 6.12. It changes no installed file.

Corresponding source. The base is Qt's released qtwebengine-everywhere-src-6.11.2.tar.xz, which carries the Chromium tree it builds. The changes are the twenty patches in patches/ of omaweb-qtwebengine-patches at 32be1d7, each a single commit with its own reasoning, and on x86_64 toolchain/clang.patch, which changes how the engine is compiled and not what its code does. packaging/MODIFICATIONS.md in the package says the same and ships with it, alongside the LGPL-3.0 text and Chromium's own notice taken from the tree the engine was built from.

The signed copy lives in Omaweb's pacman repository, which is where a reader gets it. The packages here are unsigned, and they are the artifacts the publishing workflow signs.

What it was tested against.

• verify-x86_64.txt and verify-aarch64.txt are the gate from the builds these packages carry. Each read V8's ninja file and found it compiled with its write barriers, then passed 37 of 37, 10 of 10 and 3 of 3, including the new anOffscreenDocumentCanBeCreated. Neither container had a stock engine, so the stock comparison was skipped.
• x86_64 was built with clang, LLD, ThinLTO and Chrome's PGO profile in an Arch container on a Ryzen 7 PRO 7840HS. aarch64 was built with GCC in an arm64 Arch container on an Apple M2 Max, incrementally from the 6.11.2-5 tree. Each package holds 599 files.
• A minimal extension that calls chrome.offscreen.createDocument() crashes with SIGSEGV on 6.11.2-5 and runs on this x86_64 build, from its page and from its service worker.