Bug 861370 - strange problems on TTY1 (password in clear / auto-complete and history won't work )
Summary: strange problems on TTY1 (password in clear / auto-complete and history won't...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-28 11:39 UTC by freeeaks
Modified: 2013-03-28 14:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-28 14:04:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description freeeaks 2012-09-28 11:39:09 UTC
Description of problem:
- my tty1 show my password in clear when i'm login in.
- after being logged in, auto-completion doesn't work: pressing tab key gives a tab space instead of command auto-completion.
- trying to access command history by pressing up and down arrow key gives output like " ^[~A " instead of showing terminal commands history.

i boot in run level3. when machine finishes booting up i'm in TTY1

Version-Release number of selected component (if applicable):


How reproducible:
anytime. but it seems to happen only in TTY1.

Steps to Reproduce:
1.change default.target to point to multi-user.target (boot in run level 3)
2.log in.
3.try up and down arrow keys.
4.try command auto-completion with tab key.
  
Actual results:
1.boot in run level 3 ok
2.while login in: password is shown in clear
3.command history doesn't show up
4.tab key gives tab spaces instead of completion.

Expected results:
1.boot in run level 3 ok
2.while login in:password should not be shown in clear
3.command history should shown up
4.tab key should auto-complete commands


Additional info:
seems to happen only in tty1

Comment 1 Josh Boyer 2013-03-12 19:48:45 UTC
Are you still seeing this with 3.7.9 or 3.8.2 in updates-testing?

Comment 2 Josh Boyer 2013-03-28 14:04:19 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a
response in 2 weeks.  If you are still experiencing this issue,
please reopen and attach the relevant data from the latest kernel you are
running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.