GNOME Bugzilla – Bug 355307
If uncompressed name not specified in compressed file, cannot view, bad extracted filename
Last modified: 2006-10-22 00:57:53 UTC
Please describe the problem: If a compressed file is created with | gzip > the extracted filename has backslashes that don't belong in it. For example, trying to view a compressed plaintext file named foo(4).log.gz from file-roller using gedit causes gedit to open /tmp/*/file(4).gz which appears blank since the actual filename extracted to is /tmp/*/file\(4\).gz Steps to reproduce: $ echo omgponies | gzip > 'x$x\x'\''x`x\x"x\x!x?x*x x(x)x[x]x&x|x:x;x<x>x.gz' $ file-roller 'x$x\x'\''x`x\x"x\x!x?x*x x(x)x[x]x&x|x:x;x<x>x.gz' Archive -> Extract... [Extract] Archive -> Quit $ ls Actual results: x\$x\\x\'x\`x\\x\"x\\x\!x\?x\*x\ x\(x\)x\[x\]x\&x\|x\:x\;x\<x\>x x$x\x'x`x\x"x\x!x?x*x x(x)x[x]x&x|x:x;x<x>x.gz Expected results: x$x\x'x`x\x"x\x!x?x*x x(x)x[x]x&x|x:x;x<x>x x$x\x'x`x\x"x\x!x?x*x x(x)x[x]x&x|x:x;x<x>x.gz Does this happen every time? #t Other information:
> plaintext file named foo(4).log.gz from file-roller using gedit causes gedit to > open /tmp/*/file(4).gz which appears blank since the actual filename extracted > to is /tmp/*/file\(4\).gz er, that's foo(4).log.gz and /tmp/*/foo(4).log and /tmp/*/foo\(4\).log respectively of course. I blame backslash blindness ;)
fixed in current CVS; thanks.