From Bugzilla Helper: User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.9-6custom i686; Nav) Description of problem: Changing runlevels to runlevel 1 results in an usable terminal. The command line buffer is executed on character at a time ('ps' results in 'p': command not found). Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.boot runlevel 3 2.int 1 3.type any command Actual Results: Any command is parsed one character at a time. 'ps' first results in 'p: command not found'. Then just hitting Enter once, gets a 's: command not found'. Any command longer than one character does not work. Expected Results: Proper command execution. Additional info: Booting runlevel 1 works fine. Booting runlevel 1, then changing to 3 works fine. Default shell is bash. This started after applying all recent updates as a group (glibc, filesystem, etc). So I am not sure the util-linux update is the culprit here. Also, the prompt is screwy and alternates between what should be a normal looking rootshell prompt and my personal user bash prompt: 2.4-sh# [hal@feenix hal]$ 2.4-sh# [hal@feenix hal]$ 2.4-sh# [hal@feenix hal]$ 2.4-sh# [hal@feenix hal]$ 2.4-sh# [hal@feenix hal]$ Consistently, after each command.
> Any command longer than one character does not work. After the error has happened once, entering a longer command or pressing return a few times, seems to fix the virtual terminal (for me) for some time. The probability of reproducing this bug increases with a newly booted machine at run-level greater than 1, and then either run "init 1" or switch to a virtual terminal and log in as root.
What SysVinit are you running?
SysVinit-2.78-17 which has been an errata update for Seawolf. That single "bash: No job control for this shell" message from bug #54741 applies here, too. FWIW, the problem seems to be gone with Enigma.
SysVinit-2.78-17 here also.
*** Bug 55545 has been marked as a duplicate of this bug. ***
after downgrading to util-linux-2.10s-13.7 from the 7.1 errata the symptom (also descripted in bug # 55545) disappeared, so I think this is the place where the bug sits :)
*** Bug 46223 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 54741 ***