The va-driver is included by intel-media-driver. For this SRU, base on my knowledge. GL and VK tests are passed. So set verification-done.
** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2111480 Title: Backport packages for 24.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in glslang package in Ubuntu: Invalid Status in llvm-toolchain-20 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-20 package in Ubuntu: Invalid Status in spirv-tools package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in directx-headers source package in Noble: Fix Committed Status in glslang source package in Noble: Fix Committed Status in llvm-toolchain-20 source package in Noble: Deferred Status in mesa source package in Noble: Fix Committed Status in mesa-amber source package in Noble: Fix Committed Status in spirv-headers source package in Noble: Fix Committed Status in spirv-llvm-translator-20 source package in Noble: Deferred Status in spirv-tools source package in Noble: Fix Committed Status in wayland-protocols source package in Noble: Fix Committed Bug description: [Impact] The graphics HWE stack from plucky needs to be backported for 24.04.3 directx-headers - backport from plucky - bumped build-dep of mesa glslang - backport from plucky - required due to updated spirv-tools spirv-headers - backport from plucky - build-dep of new spirv-tools spirv-tools - backport from plucky - has a bugfix that the intel shader compiler needs - NOTE! the current version in noble FTBFS even without any updates enabled, but this version builds, hence the full backport instead of just patching the current one wayland-protocols - bumped build-dep of mesa - note: this is NOT the version from plucky, which would require a newer wayland as well, but instead the oldest update to make mesa happy mesa-amber - libglapi library got merged in mesa-libgallium but it can't be directly used by external dependencies, so instead we'll have mesa-amber build libglapi- amber which Provides libglapi-mesa mesa - new major release, last of the series (25.0.7) so it has accumulated all the fixes upstream considered worthy for it - new HW support, bugfixes [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA driver after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible mesa-amber: - install libgl1-amber-dri, check that libglapi-amber gets installed and there are no conflicts - ideally, test also on gen4/gen5 Intel GPU's that things still work - test that src:primus builds and binaries install without changes and in each case check that there is no gfx corruption happening or worse. Also test WebGL on a browser like Firefox/Chromium - open https://webglsamples.org and run some demos Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with plucky, we'd already know if there are serious issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2111480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
