Engine 6.11.2-3

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-2. The Qt release and the Chromium it carries are the same: QtWebEngine 6.11.2 on Chromium 140.0.7339.225, with Chromium security fixes up to 151.0.7922.71. Three patches were added to the series:

• A request interceptor can ask for the DNS aliases of the host a request goes to (villekivela/omaweb-qtwebengine-patches#5). Content blocking uses this to refuse a tracker hidden behind a CNAME.
• QWebEngineLoadingInfo reports the certificate chain a page arrived over (villekivela/omaweb-qtwebengine-patches#6, Omaweb's ADR 0054). Site information shows it.
• The perfetto trace-category lookup is done at compile time again (villekivela/omaweb-qtwebengine-patches#1). It merged after 6.11.2-2 was packaged, so this is the first published build that carries it.

The package also records the correct checksum for MODIFICATIONS.md (villekivela/omaweb-qtwebengine-patches#7).

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.

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 seventeen patches in patches/ of omaweb-qtwebengine-patches at 6e3e278, each a single commit with its own reasoning. 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.

What it was tested against.

• verify-x86_64.txt and verify-aarch64.txt are the gate from the builds these packages carry. Each passed 36 of 36, 10 of 10 and 3 of 3. The x86_64 build ran on a rented machine, and the aarch64 build ran locally.
• Each package was installed into a clean Arch container on its architecture, and ldd resolved every library in /usr/lib/omaweb apart from Qt Designer's, which the optional Designer plugin needs. The testbrowser example in lib/qt6/bin does not find the engine libraries without LD_LIBRARY_PATH. 6.11.2-2 shipped it the same way, and Omaweb does not use it.
• Omaweb at a8868a7 was built against the aarch64 package on the Omarchy VM. Its engine contract and certificate-chain tests passed, and the certificate view was checked by hand on a live Hyprland session.