After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 590468 - file-roller-2.27.2+ won't archive files with spaces (" ") in them
file-roller-2.27.2+ won't archive files with spaces (" ") in them
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
2.27.x
Other All
: Normal normal
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2009-08-01 16:22 UTC by Andreas Olsson
Modified: 2009-08-02 08:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Andreas Olsson 2009-08-01 16:22:21 UTC
Please describe the problem:
File-roller as of version 2.27.2 and newer won't archive files with spaces (" ") in them. It seems as the underlaying layer/command doesn't accept the format in which file-roller passes the file name.

First saw this problem in the Ubuntu version 2.27.3-0ubuntu1 of file-roller. Went on to try building different versions of file-roller from original source packages, using default ./configure. File-roller 2.27.1 and earlier handled the spacy-filenames just fine, while the versions 2.27.2 and 2.27.3 ran into said problem. 

Steps to reproduce:
1. Create a file, containg a space (" ") in its name. Let us say "hello world" as an example.
2. Start file-roller
3. Create an archive of type tar, ar or jar
4. Try adding the file from step 1


Actual results:
I recieve an error such as this.

tar: hello%20world: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

The file is not added to the archive

Expected results:
The file to be added to the archive, without any error message.

Does this happen every time?
Yes

Other information:
Originally reported as a Ubuntu bug in Launchpad, https://bugs.launchpad.net/bugs/406762
Comment 1 Paolo Bacchilega 2009-08-02 08:35:53 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.