I see, when the file literally has a %20 in the name, file-roller
converts it to a space before calling tar, which fails since the file
name does not have a space in it.
** Package changed: tar (Ubuntu) => file-roller (Ubuntu)
** Changed in: file-roller (Ubuntu)
Importance: Undecided => Medium
** Changed in: file-roller (Ubuntu)
Status: Incomplete => Triaged
** Summary changed:
- tar.gz stops with error "unable to execute stat no such file or directory" on
files like bla%20bla%20bla.jpg
+ File-roller unescapes %xx sequences in file names before calling tar
** Description changed:
- Binary package hint: tar
+ Create a file with a %20 in the name, like "New%20File" ( instead of
+ "New File" ). Right click and choose compress. When file-roller calls
+ tar, it errors out saying it can not stat "New File", since the file
+ name is actually "New%20File".
- tar.gz stops with error "unable to execute stat no such file or
- directory" on files like bla%20bla%20bla.jpg
-
-
- I back up my files for years now with tar.gz via Nautilus. Since Maverick tar
fails on a hugh number of files which includes umlauts and %20. Before Maverick
it worked a 100%.
+ file-roller should not unescape %xx sequences in file names.
--
File-roller unescapes %xx sequences in file names before calling tar
https://bugs.launchpad.net/bugs/666621
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in ubuntu.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs