no tab completion on path that contains a space

confirmed working fine in Jaunty, confirmed broken as described in Karmic.

Glad it's not just me, thought I was losing my mind or my tab key was flaking out or something. >.<

Broken in Karmic here as well, seems to coincide with the introduction of bash 4.

To get tab completion working again I used a relatively ancient version of /etc/bash_completion (RELEASE: 20060301) in combination with the existing /etc/bash_completion.d directory. This file (which comes from an earlier Ubuntu-release, ask me not which as I found it as /etc/bash_completion.ucf-old indicating it was replaced sometime in the past by the ucf (man 1 ucf) program on a machine which has not seen a clean install since 6.04) seems to work OK, it might not offer all the niceties (whatever those may be) of more recent bash completion developments but it works with spaces...

The file is attached to this message. You know the standard drill about using script/program files you download from the net... do a diff -u between the current version of /etc/bash_completion and this one to see what changed... to use this file just copy it to /etc/bash_completion after moving the original /etc/bash_completion to /etc/bash_completion.org or something similar.

I have the same bug also and just found if I used backslash before the command it works. e.g
munzir@dv6:~$ \cat foo\ foo/<TAB>
works!

In Karmic, I am experiencing the same issue as described. I did not have this issue before I upgraded from Jaunty to Karmic.

Munzir Taha's wonderful workaround works for me.

i've experienced the same problem with #
$ less \#ubuntu-<tab><tab>
#ubuntu-motu #ubuntu-server
$ less \#ubuntu-m<tab> <--- nothing happens

I think the problem is that bash-completion isn't reading escaped characters correctly.

Odd...as I'm not seeing this problem at all on my Karmic install.

Architecture: amd64
DistroRelease: Ubuntu 9.10
Package: bash-completion 1:1.0-3ubuntu1
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Please update to Beta and verify this bug still exists.

On Fri, Oct 02, 2009 at 04:15:00PM -0000, Robbie Williamson wrote:
> Please update to Beta and verify this bug still exists.
>
> ** Changed in: bash-completion (Ubuntu Karmic)
> Importance: Undecided => Low
>
> ** Changed in: bash-completion (Ubuntu Karmic)
> Status: Confirmed => Incomplete
>

yes, I can confirm it's still broken.

If I start bash without the bash-completion, it works:

    $ bash --norc
    bash-4.0$ ls Ubuntu\ One/<TAB>
    060428-bagger288-garzweiler.jpg Shared With Me@
    Pics/ stats/

but if in that same shell I load in the completion,

    bash-4.0$ . /etc/bash_completion
    bash-4.0$ ls Ubuntu\ One/<TAB>

completion stops working.

 status confirmed

yes, I can confirm it's still broken.

If I start bash without the bash-completion, it works:

    $ bash --norc
    bash-4.0$ ls Ubuntu\ One/<TAB>
    060428-bagger288-garzweiler.jpg Shared With Me@
    Pics/ stats/

but if in that same shell I load in the completion,

    bash-4.0$ . /etc/bash_completion
    bash-4.0$ ls Ubuntu\ One/<TAB>

completion stops working.

This bug was fixed in the package bash-completion - 1:1.0-3ubuntu2

---------------
bash-completion (1:1.0-3ubuntu2) karmic; urgency=low

  * Backport quote_readline fix for bash 4, since double-quoting for compgen
    is no longer necessary (LP: #419509).

 -- Colin Watson <email address hidden> Mon, 05 Oct 2009 17:28:03 +0100

I am still seeing this in 1:1.0-3ubuntu2. I've taken bash_completion out of my .bashrc to make shells usable again.

Still broken in Karmic with the latest version of bash-completion. I tried putting the file from comment #4 in /etc/bash_completion.d/ and when I launched a new terminal it just hung and never got to a point where I could enter any commands.

Works for me, and I do have bash_completion installed and enabled in .bashrc.

seems fixed for me. adam could you try making a new user account and see if it affected?

Hmm, seems to be working now. Maybe I just had to log out and then log back in or something. I thought opening a new terminal would be good enough. At any rate, I'm glad to have my tab-completion back. :-)

I'm reopening this bug cause of I cannot complete sudo mount if label of the usb key contains a space.

Step to reproduce:
Mount a key with a label lihke "foo foo"

type:

sudo umount /media/foo<TAB>

this command doesn't show
/media/foo\ foo

Nobody answer me?

I can't test karmic, but your unmount example works just fine on lucid.