Debian Patches

Status for qt6-base/6.10.2+dfsg-6

Patch Description Author Forwarded Bugs Origin Last update
upstream_hdr_vulkan.diff rhi: vulkan: Fix unintentional SDR format selection
I needed to read back the swapchain image for my Vulkan RHI-enabled
QtQuick application, but it complained that
VK_FORMAT_A2R10G10B10_UNORM_PACK32 wasn't able to be read back - why?

My initial naive solution is to simply add it to the
swapchainReadbackTextureFormat function - but that wouldn't work as
there is no BGR10A2 RHI texture format and applications would unkowingly
end up with swapped channels. The actual problem came down to how we
were selecting swapchain image formats.

The first thing I changed was the hdrFormatMatchesVkSurfaceFormat
function, because that checked two formats for HDR10:
VK_FORMAT_A2B10G10R10_UNORM_PACK32 and
VK_FORMAT_A2R10G10B10_UNORM_PACK32. Checking the online Vulkan hardware
database, the BGR variant is more well-supported. Picking the RGB
variant is inevitably going to lead into the problem described before -
and should be added back when & if a new RHI texture format is
introduced.

The next thing I changed was the swapchain format selection logic,
specifically the choice for a non-sRGB SDR format. Judging by the
comments in this function and other RHIs like DX12 we *want* the default
color format of VK_FORMAT_B8G8R8A8_UNORM unless otherwise requested.
That isn't what was happening though, on my specific hardware it was
choosing VK_FORMAT_A2R10G10B10_UNORM_PACK32 - why?

It comes down to the isSrgbFormat check in the loop. Again, for the
non-SRGB SDR case the "srgbRequested" variable is always false. And when
a non-SRGB format (like the aforementioned problematic VkFormat) is
checked isSrgbFormat will return false, but I don't think that's what is
intended here. We want that for the sRGB case, but for non-SRGB SDR the
default color format is fine and that lines up with other RHIs
(see QD3D12SwapChain::chooseFormats for an example.) I checked this
inside the loop so the passthrough code is still ran on Wayland, but I
think the new logic is still sensible.

I tested this against the five usual cases I could think of and now the
format selection seems sensible:
* non-sRGB SDR chose VK_FORMAT_B8G8R8A8_UNORM
* sRGB SDR chose VK_FORMAT_R8G8B8A8_SRGB
* extended sRGB Linear chose VK_FORMAT_R16G16B16A16_SFLOAT
* HDR10 chose VK_FORMAT_A2B10G10R10_UNORM_PACK32
* Display P3 chose VK_FORMAT_R16G16B16A16_SFLOAT

(cherry picked from commit 2dd1aa3678d541aef15b564b4013728ed5b0387b)
(cherry picked from commit f4c5e54a8703944ec7ea005ad4de3072b86fd61f)		 Joshua Goins <joshua.goins@kdab.com> no 2026-02-10
Add-SH-detection.patch Add SH description Upstream processes archs from time to time and tends to disable those that
they do not know wether they are working or not.
.
SH is working on Debian, so as an intermediate measure re enable it here.		 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> no debian
remove_privacy_breaches.diff remove non-used privacy-breach code This code makes Lintian unhappy. But we are really not using it, it only
gets inserted when building the online doc.
Anyways the best way to calm down Lintian is to simply remove it.		 Lisandro Damián Nicanor Pérez Meyer <lisandro@debian.org> not-needed 2015-02-18
build_path_embedded_qtbuildinternalsextra_cmake.patch cmake/QtBuildInternalsExtra.cmake.in: Patch out embedded build path.

The original build path should not be needed in the shipped package,
and causes reproducibility issues when built in different paths.

https://reproducible-builds.org/docs/build-path/		 Vagrant Cascadian <vagrant@reproducible-builds.org> no 2022-02-25
cross.patch no
remove_rpath_from_examples.patch remove RPATH/RUNPATH from examples' binaries. On Debian the examples are built against system's libraries, so there is no
need to set RPATH/RUNPATH.		 Lisandro Damián Nicanor Pérez Meyer <lisandro@debian.org> not-needed 2024-02-15
forkfd_grow_stack_upwards_on_hppa.patch Change how stack grows on HPPA. On HPPA stack grows upwards. This patch introduces this change for
this 3rd party code.		 John David Anglin <dave.anglin@bell.net> no debian 2023-07-28
enable_skip_plugins.patch Enable skipping plugins search at build time. This patch sets
QT_SKIP_AUTO_PLUGIN_INCLUSION and QT_SKIP_AUTO_QML_PLUGIN_INCLUSION to ON
by default, thus avoiding unnecesary build dependencies on plugins.
.
The variables can still be set to OFF by the user at build time, allowing
them to find the packages if necessary. But if you need so for a Debian
package please reach the Qt maintainers first. We want to know why you
need to do so. Thanks in advance!		 Lisandro Damián Nicanor Pérez Meyer <lisandro@debian.org> not-needed

All known versions for source package 'qt6-base'

Links