https://bugs.kde.org/show_bug.cgi?id=410160
Bug ID: 410160
Summary: Not respecting "Preserve paths when extracting"
Product: ark
Version: 19.04.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: elvis.angelac...@kde.org
Reporter: iguanamiy...@yahoo.com
CC: rthoms...@gmail.com
Target Milestone: ---
SUMMARY
Ark does not respect "Preserve paths when extracting" in case you want to
extract files from archive multiple times with and then - without that
particular setting enabled.
STEPS TO REPRODUCE
1. Open an archive with ark as root
2. Right click any file/folder and Extract > Extract to...
3. Enable "Preserve paths when extracting"
4. Extract the file/folder
5. Delete entirely the new path you just created
6. Right click the same file and again Extract > Extract to...
7. Disable "Preserve paths when extracting"
8. Extract the file/folder to the same path as per #4 above
9. Even you have deleted the previously extracted items, ark complains "This
action will overwrite the destination."
OBSERVED RESULT
Step #9 above is critical, since ark doesn't follow the new (disabled) setting
for "Preserve paths when extracting" with the new extraction. Second issue: in
#5 above I deleted the previous extraction, but in #9 it complains about the
duplicate destination file that doesn't exist??
EXPECTED RESULT
Ark should update its settings from a popup window for each and every
extraction individually.
Ark should not complain reg. duplicate destination files/folders in case
previous files/folders don't exist at the destination path anymore. I guess
this is due to extracting into temporary folder first, which may cause this
issue, but it's misleading, confusing and not user friendly.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Linux
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0
ADDITIONAL INFORMATION
During "File Already Exists" message, Ark displays the size of Source AND
Destination as 0 B, which is wrong for Source! Since Destination file doesn't
exist, it's ok to display its size as 0 B, but source obviously contains
something within and couldn't be 0 B.
--
You are receiving this mail because:
You are watching all bug changes.
