After some further investigation I realized that the message that makes
the difference in the log file (Operation-Ending-Supplemental Code is
0x27) does not come from QPDF but rather from the s390x's DFLTCC
hardware-accelerated deflate that zlib uses.
For testing purposes I have build plucky zlib for noble (available at
ppa:dgadomski/s390-builds).
It contains a number of s390-related updates. I am looking into the details to
backport what is needed to fix that to jammy & noble.
** Also affects: zlib (Ubuntu)
Importance: Undecided
Status: New
** Changed in: zlib (Ubuntu Jammy)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: zlib (Ubuntu Noble)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: qpdf (Ubuntu)
Status: New => Invalid
** Changed in: qpdf (Ubuntu Jammy)
Status: New => Invalid
** Changed in: qpdf (Ubuntu Noble)
Status: New => Invalid
** Summary changed:
- fuzz-16214 test failing on s390x
+ qpdf fuzz-16214 test failing on s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2131944
Title:
qpdf fuzz-16214 test failing on s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/2131944/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
