When I enter a Username at the login prompt using all Capitalized letters every text is printed in Capitalized Letters and no Color and Sytel Attributes are displayed. Ncurses or dialog based applications dont work (they hardly display anything) Reproducible: Always Steps to Reproduce: For example: 1. Goto Login Prompt 2. Enter "ROOT" (all capitalized letters) 3. Press Enter Now it displays "PASSWORD: " instead of "Password: " 4. Enter your Password 5. Press Enter "LAST LOGIN: MON OCT 6 21:46:22 ON 5" is also displayed in capitalized letters. Now the promt appears all capitalized without Colors. Start an application like ufed or menuconfig or net-setup to see whats happening with these. To return to a normal prompt either 6.1 Logout turn off caps-lock, enter a username with non capitalized letters in it and login with it. or 6.2 Enter "reset <Enter>" at the prompt. It doesn't matter if you activate Caps-Lock or not. This bug appears every time you enter an all capitalized username at the login prompt.
yeah, i noticed that if you log out and play around with turning on/off capslock it goes away ...
But first of all it should not come. Because if it's not comming there is nothing we have to make go away! :) mfg Nomike aka Michael Postmann
I can confirm. I do not know when I will be able to try and track this ... Solar, if you not too busy, mind giving you detective skills a flex ? :)
If you enter your username on the login prompt all in capitals then the login progam will be lead to believe that you have an upper-case only terminal (pretty rare devices these days but once upon a time they ruled the desktop). You will then enter into the system where uppercase letters rule. This is a feature and not a bug! Make sure your disable capslock before entering your userid. Reference: http://www.togaware.com/linux/survivor/All_Capitals.html
sounds good to me :)
*** Bug 81160 has been marked as a duplicate of this bug. ***
*** Bug 100416 has been marked as a duplicate of this bug. ***
*** Bug 107771 has been marked as a duplicate of this bug. ***
*** Bug 144457 has been marked as a duplicate of this bug. ***
