Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Something strange started happening to my terminal. Whenever I type some wrong command it tries to run that command in the background.

hegeek@colinux: ~# l   
[9]+  Stopped   l  
thegeek@colinux: ~# fdsl  

[10]+  Stopped                 fdsl  

What could be the issue?


After restarting the system the issue is solved. But I am still curious what caused this issue. I think it has to do something with command_not_found_handle shell function. While trying to find the command, it was doing something weird.

share|improve this question
What output do you get from the alias command? – Warren Young Sep 3 '10 at 22:09
just one "alias ls='ls --color=auto'". Its an new colinux installation. – Hemant Sep 3 '10 at 22:13
Does saying /bin/sh -l fix it? If not, what about switching to another shell, like tcsh -l? – Warren Young Sep 3 '10 at 22:17
this is a weird problem +1 because I've no clue. – xenoterracide Sep 4 '10 at 0:39
@Warren Young: After restarting ubuntu this problem solved. But I dont know what caused it. – Hemant Sep 4 '10 at 4:31

That sounds like the command-not-found hook was acting up for some reason. I've had problems with it before, but never could figure out how to fix it :-/.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.