Engine 6.11.3-1

QtWebEngine 6.11.3 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-16. QtWebEngine 6.11.3 on Chromium 140.0.7339.264, carrying Chromium's security fixes up to 155.0.8059.85, where 6.11.2 stopped at 151.0.7922.71. This release is for those security fixes (Omaweb's #802, #822).

6.11.3 makes two of the series' changes itself, so the series is thirty-one patches instead of thirty-three:

• The pure-computation seatbelt profile name is gone, because 6.11.3 no longer has Seatbelt::kProfilePureComputation to define.
• V8's write barriers are on by Qt's own setting now, so the patch that turned them back on is gone. The gate still reads the built tree and fails if a later Qt turns them off again.

The other thirty-one apply unchanged, with no conflicts, and are renumbered.

Each package names the Qt it was built against. The engine uses Qt's private API, so it runs on the Qt it was built against or a newer one. Each package's qt6-base and qt6-declarative floor is that Qt, 6.12.0, and the module's version is pinned to 6.11.3.

Corresponding source. The base is Qt's released qtwebengine-everywhere-src-6.11.3.tar.xz, which carries the Chromium tree it builds. The changes are the thirty-one patches in patches/ of omaweb-qtwebengine-patches at 417d413, 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.

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. omaweb-qtwebengine-6.11.3-x86_64.tar.zst and omaweb-qtwebengine-6.11.3-aarch64.tar.zst are the install trees the packages were made from.

What it was tested against.

• x86_64 was built against Qt 6.12.0 from Omarchy's stable mirror, with clang 23, LLD, ThinLTO and Chrome's PGO profile in an Arch container. The -16 tree was brought to 6.11.3 with the tarball-to-tarball diff and the series applied, giving trees byte-identical to a fresh one, and about 40% of the build rebuilt. It depends on qt6-base>=6.12.0.
• verify-x86_64.txt is that build's gate. It found a font to draw test pages in and V8 compiled with its write barriers, then passed 63 of 63, 10 of 10, 3 of 3, 9 of 9, 3 of 3, 7 of 7 and 13 of 13.
• aarch64 was built against Arch Linux ARM's Qt 6.12.0 with GCC in an Arch Linux ARM container. It depends on qt6-base>=6.12.0.
• verify-aarch64.txt is that build's gate, with the same sections as x86_64's passing in full: a font found, V8 with its write barriers, then 63 of 63, 10 of 10, 3 of 3, 9 of 9, 3 of 3, 7 of 7 and 13 of 13.
• Neither container had a stock engine, so the stock comparison was skipped.
• Unlike earlier engine releases, neither package has yet been installed in a fresh container with Omaweb's engine contract suite run against it.