Comment 0 for bug 1242169

I'm not sure that this is the right package to report this problem, but as I understand it is responsible for keyboard stuff and it was significantly changed in Saucy.

I noticed some strange and annoying behaviour in gnome terminal window. If you type some command with single pipe (|), double pipe (||) or double ampersand (&&), you'll see that bash can't recognize the command after the pipe/ampersand.

Example:

anton@ibn-hottab:~$ ls | grep Music

No command ' grep' found, did you mean:
 Command 'fgrep' from package 'grep' (main)
 Command 'vgrep' from package 'atfs' (universe)
 Command 'xgrep' from package 'xgrep' (universe)
 Command 'grep' from package 'grep' (main)
 Command 'zgrep' from package 'gzip' (main)
 Command 'zgrep' from package 'zutils' (universe)
 Command 'igrep' from package 'openimageio-tools' (universe)
 Command 'agrep' from package 'agrep' (multiverse)
 Command 'sgrep' from package 'sgrep' (universe)
 Command 'rgrep' from package 'grep' (main)
 Command 'dgrep' from package 'debian-goodies' (main)
 Command 'ngrep' from package 'ngrep' (universe)
 Command 'lgrep' from package 'lv' (universe)
 Command 'pgrep' from package 'procps' (main)
 Command 'egrep' from package 'grep' (main)
 grep: command not found

I'm 100% sure that grep is installed on my computer. And in fact it doesn't matter what command is entered after the pipe. As you may notice Space symbol is enterpreted as a part of the command.

But if you press Up and remove or edit the space in the command, it will work fine:

anton@ibn-hottab:~$ ls | grep Music
Music

I understood why this happened. When I typed the command fast, I press Shift to enter the pipe and then emmidiately press Space. In other words, when I type Shift + Space some strange symbol that looks like a space entered instead (nobreakspace maybe) that is enterpreted by bash as a part of the next command. If you type the command very carefully and don't press Shift when enter the Space, everything will work as expected.

I veryfied this bug in gnome-terminal and in xterm and it is 100% reproducible. There is not difference if I'm using bash or sh. The bug is not reproducible at all when I test in real terminal (tty, Ctrl+Alt+F1).

Please, let me know if you need some assistance from my side.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Sat Oct 19 23:42:44 2013
InstallationDate: Installed on 2011-02-12 (979 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MarkForUpload: True
SourcePackage: indicator-keyboard
UpgradeStatus: Upgraded to saucy on 2013-10-18 (1 days ago)