GNOME Bugzilla – Bug 314030
Error view tar.gz contents when temporarily extracted to /tmp more than once
Last modified: 2006-03-19 19:43:36 UTC
Distribution/Version: Fedora Core 4 I'll describe a situation here where I try to open the file-roller sources (tar-gzipped) from Mozilla Firefox 1.0.6 on Fedora Core 4 with file-roller 2.10.0. However, I it's easy to reproduce the bug using other applications like a mail client as well. Specifically, I've also reproduced the bug by trying to open a tar.gz attachment from Mozilla Thunderbird 1.0.6. What happens: 1) In Mozilla Firefox, download the tar.gz file mentioned below (or any other tar.gz file for that matter): (http://ftp.gnome.org/pub/gnome/sources/file-roller/2.10/file-roller-2.10.3.tar.gz) 2) When asked "What should Firefox do with this file?", choose to "Open with" file-roller (it appears in the combo-box as Archive Manager on most Fedora/Gnome installations). 3) A new file-roller window opens up showing the contents of the tar.gz file (a directory named file-roller-2.10.3), which is normal and expected. 4) Repeat steps 1 and 2 above for the same file. 5) A new file-roller window appears, but instead of showing the directory as in step 3, it now shows a file named file-roller-2.10.3.tar-1, file-roller-2.10.3.tar-2, file-roller-2.10.3.tar-3, and so on with successively increasing numbers at the end every time steps 4 is executed. 6) Upon deleting /tmp/file-roller-2.10.3.tar*, the contents are displayed correctly once, and the problem repeats on every successive attempt. What you would expect to happen: The contents of the tar.gz file should always be correctly and consistently displayed after recursive extraction, irrespective of the number of attempts. Specifically, the behavior in step 5 should not happen instead of the expected behavior as in step 3. The temporary extraction of the .tar file should be transparent to the user.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 166325 ***