| Summary: | KXzFilter broken for some large archives | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-karchive | Reporter: | Ragnar Thomsen <rthomsen6> |
| Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | faure, helio, kdelibs-bugs-null, peroyvind |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Ragnar Thomsen
2015-05-22 22:14:15 UTC
I inserted some qDebug statements to see at which file in the archive the assertion failure occurs. For the linux-3.12 source, it always happens when extracting the file: drivers/media/dvb-frontends/s5h1411.c When opening this file in a text editor I can see that it is truncated, although not always at the same position. I've tried extracting other kernel source versions and the assertion failure occurs when extracting different files, but always the same for the same archive. Have investigated this further. Tried extracting the xz-compressed tarball of the Qt-5.4.1 source (which is much larger than the kernel-3.12 source, 278MB and 75MB, respectively). This was possible without error, so this issue might be specific to some kernel source archives. Tried decompressing linux-3.12.tar.xz with xz (v5.2.1) and re-compressing it. The re-compressed archive opened/extracted without issues in Ark using karchive plugin. Tested the kernel source archive using xz -t, which could not detect any issues with the archive. Do you have a link to the problematic xz archive, so I can be sure we're not testing something slightly different? Here's the link to the linux kernel source v3.12: https://www.kernel.org/pub/linux/kernel/v3.0/linux-3.12.tar.xz Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. |