https://bugs.kde.org/show_bug.cgi?id=464734
--- Comment #2 from Adrien Beau <abe.kde.b...@zerty.xyz> --- Investigating further, another library is a more likely suspect, upgraded at the same time: qt5-image-formats-plugins:amd64 was upgraded from version 5.15.8+p22.04+tunstable+git20230110.1648-0 to version 5.15.8+p22.04+tunstable+git20230119.0121-0 The previous good build was https://build.neon.kde.org/view/3%20unstable%20%E2%98%A3%20git%20master/job/jammy_unstable_qt_qtimageformats/20/ The bad build is https://build.neon.kde.org/view/3%20unstable%20%E2%98%A3%20git%20master/job/jammy_unstable_qt_qtimageformats/21/ I don't see obvious errors in the build outputs. I see that different revisions of the kde/5.15 branch in the https://invent.kde.org/qt/qt/qtimageformats repo were built. Revision abe44c0f526e499668b1131c5990d9b571f99c46 is good. Revision dbc9c396199ef78e820b40ddb8a4e76c0a86d48c is bad. Looking at the 3 commits on that branch between the two revisions, I see a suspicious commit: Implement support for file memory mapping for tiff reading https://invent.kde.org/qt/qt/qtimageformats/-/commit/c5c49dd6249c5e12e6aed3e240f485fb3b56ad31 I understand this is a KDE-maintained branch, should I report the issue somewhere else on this bugtracker, or add the committer to the CC List of this bug? -- You are receiving this mail because: You are watching all bug changes.
