Red Hat Bugzilla – Bug 160703
Files are not saved when extracting archive
Last modified: 2007-11-30 17:11:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
I recently upgraded from FC3 to FC4. Prior to the upgrade, I utilized file-roller often and never had any issues. When I open an archive (only tested on tar.gz files) and extract it, the program behaves exactly as I would expect. But, when I look in the folder where it was extracted to, it isn't there. I have plenty of available harddisk space. I also tried manually extracting them from the command line and this worked fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open archive by clicking on icon in Nautilus or automatically opening from download in Firefox.
2. Click "Extract files from the archive" button.
3. Click Exctract button.
Actual Results: Program behaved fine, but files weren't saved to disk.
Expected Results: Files should be where I tried to extract them.
Apparently, when selecting the folder to extract to, it was being extracted to
the folder that was highlited, rather than the one that was opened, as I was
accustom to. The files had been extracted all along, but in the top folder in
my diectory listing. Is this a new feature of gnome or possiblely a setting
that was changed when I upgraded?
This is actually a gtk2 filechooser bug that was fixed in 2.6.8. Patch is
available in cvs here:
Could we get gtk updated to 2.6.8, or 2.6.7 with the patch applied? File-roller
and some other apps act pretty weird without it.
*** Bug 160887 has been marked as a duplicate of this bug. ***
Reassigning to gtk2 maintainer
Thank you for the bug report. However, Fedora Project no longer maintains this
version of the product. Please upgrade to the latest version and open a new bug
if the problem persists.
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older
releases, and if you believe this bug is interesting to them, please report the
problem against Fedora Legacy component