Ok, today I wanted to decompress a gziped .iso file from an external
hard drive and was surprised when suddenly cp appeared in the gnome-
system-monitor.
So, just to be sure the problem is adressed properly: File Roller is copying
the 8 GB .gz file from my external hard drive to a folder in /home/user/.cache,
then decompresses it to the destination of the file.
This happens when compressing and decompressing .gz, .bzip2, .xz, but not with
tar.gz, tar.bzip2 and tar.xz. These are just the ones I tested, there could be
more.
This could be a good feature, as Ahmad said 4 years ago, but it is not. This is
just silly:
The gzip decompression is, in my case, as fast as the read speed of my external
hard drive. It uses just 40% of one core on my system, so it is just limited by
the copying speed. Now, when File Roller thinks it has to copy it twice, it
takes twice the time it would have to.
But there is more: I had problems becouse of this years ago, when I had only a
60GB HDD, but I didn't know why at that time. Lets say, you have a 10GB
partition image (.img) on your external hard drive, compressed with gzip
(.img.gz) which is now 6GB, thanks to the magic of gzip. You want to decompress
it to the HDD of your PC and you have 13 GB free, just right for the 10 GB
decompressed file. But this is when File Roller pisses on your great
calculation. It copys the 6GB file into your .cache directory and suddenly
there are only 7GB left on your system and File Roller fails to decompress
becouse of to few disk space. This is the worst feature that has ever been
invented.
Thanks for your attention, I am a bit angry and wanted to share my view.
By the way, does anybody konw why the GNOME people are ignoring ignoring
this now since 7 years? This is definetly not a feature, this is just
stupid.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/146206
Title:
files are copied to a local directory before being extracted
Status in File Roller:
New
Status in “file-roller” package in Ubuntu:
Triaged
Bug description:
Binary package hint: file-roller
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!
To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/146206/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
