Thank you for opening this bug and helping make Ubuntu better.
I downloaded & had a look at the tar file. First of all, your option to
set '-o' was a sane one, but it did not matter -- this is the default
for non-root users of tar.
Second, the error you are getting comes from the way the original
setting permissions to
$ chmod -R 660 abc
is no good choice as you forbid entering the directory and therefore cannot
list it.
i think extracting the archive as a non-privileged user results in a
case just like this. i think this is not a bug but unexpected behavior
due to questionable setting of
I am seeing the same corruption on two Ubuntu 7.10 systems, but for me
it happens whenever I do a recursive chmod -R on a directory.
Afterwards, the ls command shows everything inside the directory as
corrupted with question marks:
$ mkdir abc
$ mkdir abc/aaa
$ mkdir abc/bbb
$ mkdir abc/ccc
$ touc
