| Summary: | "Extract here and delete archive" deletes only the first (.part1) file for multi-part RAR archives | ||
|---|---|---|---|
| Product: | [Applications] ark | Reporter: | Dick Tracey <traceydick> |
| Component: | general | Assignee: | Elvis Angelaccio <elvis.angelaccio> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | antti.savo, eduardosareias, rthomsen6, severinvonw |
| Priority: | NOR | ||
| Version First Reported In: | 24.02.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Dick Tracey
2024-03-28 16:04:45 UTC
Hi, I can confirm this behavior on my system. I'm afraid I didn't consider multi-volume archives when implementing this feature. Unfortunately, it's also not that easy to fix: - Ark uses various plugins for different types of archives (e.g. p7zip for 7-Zip archives, unrar for RAR archives, etc.) - Most (but not all) plugins only pass the file name of the first (.part1) archive to the underlying archive program/library for extraction - The paths of the others parts are resolved internally by the program/library - Thus, we can't delete the other parts (.partX) after extraction, as we don't have their file paths To solve this issue, we could try to implement a function that finds the other parts of the archive. This is rather difficult because the .partX naming scheme is not used by all archive types (7-Zip also uses .7z.XXX for example). Isn't it better to remove/disable this functionality, at least for ".part*" archives, until a proper fix is in place? The current behavior is not good in my opinion. Bug confirmed also on my system. Nobara 40, Plasma 6.1.3, frameworks 6.4.0, Kernel 6.10.3 . It affects other compressed formats, not only RARs. 7z files with .001 , .002 etc extensions are also affected by this bug. The first one gets deleted (.001) but all the others remain. I encountered this bug today. Another year later since I last commented on this bug, I am here to confirm that this bug is still very much present and actively being ignored. June 2025, KDE Plasma 6.4 |