GNOME Bugzilla – Bug 485665
files are copied to a local directory before being extracted
Last modified: 2020-11-11 19:15:14 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/146206 "... gutsy, file-roller 2.20.0-0ubuntu1 this is big a problem, and I don't really understand why this has been done in this way before extracting files, file roller copies the archive in a local directory. If the space on the device is low, you cannot extract anything and this error is given to you: cp: write of `/home/yelo3/.fr-kw21if/lunar-1.6.2-beta1-i686.iso.bz2': No device space left file-roller should be able to extract the archive from the position it has! ... I've tested that this does not happen with zip, iso, rar files. file-roller runs: yelo3 16709 11.2 0.1 2136 736 ? S 18:34 0:05 unzip -d /home/yelo3/Scaricati/iso -o -P /home/yelo3/Scaricati/iso.zip but you can easily check this trying to un-gzip(bzip2) a big file (a file that gunzips(bunzips2) in more than a few seconds) while extracting it you can do a ps -ux and you will see: yelo3 16982 11.5 0.0 2040 496 ? R 18:37 0:04 gzip -f -d -n /home/yelo3/.fr-65rcKi/file.gz or yelo3 19326 18.1 0.7 5284 4024 ? D 18:49 0:02 bzip2 -f -d /home/yelo3/.fr-80UAsI/file.bz2 ..."
I've also commented on the Launchpad about why the implementation exists. By the way, just I have said over there, I suggest moving the uncompressed file instead of copying it, so that no unnecessary duplication is made for destination with the same drive as the temp. Or is there any other technical reason for using cp?
if the destination folder already exists mv doesn't work correctly. (more details in bug #590027)
Oh I forgot to mention that my suggested solution should apply to single compressed file, and not tarball. That way, no problem if you move it, no?
Has this get any progress in the few years? I' m experiencing a copy of 17GB file on the second drive to ~/.cache and compress to gz and copy back. This is just insane, and will hurt my SSD mounting /home.
*** Bug 545472 has been marked as a duplicate of this bug. ***
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use file-roller and if you still see this bug / want this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/file-roller/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (volunteer workforce and time is limited).