Strange BASH behavior

[abohmeed]

Hi all
I am relatively new to linux (specifically red hat). I have installed Fedora 13 on my machine and started playing with the terminal when i found a very strange behavior when typing a command that is not found:
the terminal does not prompt me back. In other words, i am logged as root (or any user) and type "bla bla bla" the bash replies "command not found" but the cursor stays besides "command not found" and does not display the prompt $(the PS1). Moreover, whatever i type in this strange phase goes without any response, be it a real command (like exit) or any garbage. This phase only ends when i press control+c.
Strange enough, when i type control-z it gives me what i typed (the grabage) and a job number and informs me that the job is stopped (as if a typed a real command that takes a lot of time to run and i am suspending it).
This behavior only happens in BASH, for when i switch to sh nothing of this happens.
Does anybody have any clue why does BASH behave like this? it is a fresh install by the way, haven't changed any parameters or settings.

Thanks

[meton_magis]

fedora 12+ added a "feature" (I hate it) that anytime a command is entered on the command line that is not found, it uses yum to search for possible programs to install that are like what you just entered. If yum is not configured to work in your current setup (or you're offline) it may hang like you're describing.

I think you can remove it in fedora 13. Just do a

`yum search yum`

and look for something along the lines of command completion, or something like that.

looking at the fedora wiki, it may be
PackageKit-command-not-found


whatever it is, run
`yum remove packagename`