Extra space is added and backslash is removed under the 'find' command

[Jindrich Liprt]

Extra space scenario:
find /op<TAB> ==> find /opt<Space>

Backslash scenario:
cd ~
mkdir -p test\ 1/test
find test\ 1/t<TAB>
find test 1/test
find: `test': No such file or directory
find: `1/test': No such file or directory
rm -r test\ 1/t<TAB>
rm -r test 1/test
rm: cannot remove `test': No such file or directory
rm: cannot remove `1/test': No such file or directory
ls -l test\ 1/t<TAB>
ls -l test 1/test
ls: cannot access test: No such file or directory
ls: cannot access 1/test: No such file or directory

etc.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bash-completion 1:1.3-1ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Wed May 16 23:50:58 2012
PackageArchitecture: all
SourcePackage: bash-completion
UpgradeStatus: Upgraded to precise on 2012-05-01 (15 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Wolfgang Betz (wbetz)]

In my case this was due to a symbolic link from /etc/bash_completion.d/acroread.sh -> /opt/Adobe/Reader9/Resource/Shell/acroread_tab. After removing the symbolic link and starting a new bash shell, things were back to normal.

... see also http://ubuntuforums.org/showthread.php?p=11941246

[Peter Cordes (peter-cordes)]

Trusty blacklists acroread.sh from bash_completion.d, so does upstream.

If you still have this on Trusty, bug 1372286 needs to know what other files to blacklist to un-break completion.

Good testcase and description of exactly what the bug is, copied it for 1372286.