Hi again,Last time I make some noise about this topic, I have also sent a patch to fix this issue on QT6 for Bookworm.
Patrick Le 22/03/2025 à 09:37, Patrick ZAJDA a écrit :
Hi Samuel and all, I have successfully tested and sent the patch to the mentioned bug.As I only have the patch for QT5, I cannot do more for now except trying to get the QT6 specific patch and build custom packages to test as I have done for QT5.I hop this will help to fix this crash on Debian. Patrick Le 20/03/2025 à 18:38, Samuel Thibault a écrit :Patrick ZAJDA, le jeu. 20 mars 2025 15:24:19 +0100, a ecrit:What could be done to have this fix backported to the version of QT5 and whynot 6 which are provided in Bookworm?You can work on the backport :) That means identifying the upstream commit that fixes the issue, try to build a patched debian package with it and confirm that this fixes the issue, and then you can send the patch to the bug tracker. Once it gets integrated into testing, we can ask for a stable update.Debian testing has a right QT6 version as fare as I know. But Bookworm not. The QT team provide patches to be ported for Linux distributions I.E. Debian and other but it looks it is not considered enough importent to be fixed inDebian as it seems, unfortunately.Determining exactly which patch actually fixes the issue, is an involved task. I'm really not surprised that the Debian maintainer hasn't taken the time to do it, because the reproduction scenario is quite involved. If you provide the patch file to the bug tracker saying "I have verified that this upstream commit, when applied on the debian package, fixes it for me", that'll be *way* easier for the Debian maintainer to accept it. Samuel
-- Patrick ZAJDA
OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
