I wish I could be more help, because this has happened to me more than twice in the not terribly distant past. I simply cannot remember any details. The only thing I seem to recall, besides being 100% en_US and using PS/2-connected keyboards, is getting back in via chroot.
On Sat 15 Dec 2018 08:36:03 PM CST, mrmazda wrote:
I wish I could be more help, because this has happened to me more than
twice in the not terribly distant past. I simply cannot remember any
details. The only thing I seem to recall, besides being 100% en_US and
using PS/2-connected keyboards, is getting back in via chroot.
Hi
Wonder if it’s one of the input packages missing?
zypper se -i input
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I doubt that it is input issue as we can type in users names to the login prompt.
VM1:~ # zypper se -i input
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+-----------------------+-------------------------------------------+--------
i+ | libinput-udev | Input device and event processing libra-> | package
i+ | libinput10 | Input device and event processing library | package
i | libxcb-xinput0 | X11 XInput Extension C library | package
i | libxcb-xinput0-32bit | X11 XInput Extension C library | package
i+ | xf86-input-evdev | Generic Linux input driver for the Xorg-> | package
i+ | xf86-input-joystick | Joystick input driver for the Xorg X se-> | package
i+ | xf86-input-keyboard | Keyboard input driver for the Xorg X se-> | package
i+ | xf86-input-libinput | Libinput driver for the Xorg X server | package
i+ | xf86-input-mouse | Mouse input driver for the Xorg X server | package
i+ | xf86-input-synaptics | Synaptics touchpad input driver for the-> | package
i+ | xf86-input-vmmouse | VMware Mouse input driver for the Xorg -> | package
i+ | xf86-input-void | Null input driver for the Xorg X server | package
i+ | xf86-input-wacom | Wacom input driver for the Xorg X server | package
i+ | xinput | Utility to configure and test X input d-> | package
i+ | xorg-x11-driver-input | Compatibility metapackage for X.Org inp-> | package
VM1:~ #
Hi
Yes, had my doubt’s as well…
So in your VM, can you change the type of keyboard to say a USB, or connect an external keyboard as a USB device in a VM and see if the issue resolves?
You could also try disabling acpi osi via the kernel option acpi_osi=
If you open a terminal in your desktop and as your user use the command chvt 1 (to get to tty1) or 2 etc (DE would normally be 7), does the issue go away?
ACPI enabled/disabled on VM - no difference for tty1-6 - mouse was flakey (Slow to move or click but still worked) in VM when disabled (documented VBox issue in 5.2 not in 5.1 fix seems to be in and out of every other release)
PS/2 Keyboard to motherboard on Host - no change
USB Keyboard to Motherboard on Host - no change
USB Keyboard attached to VM via USB 2.0 port (not main ps/2 keyboard on host) - no change
# chvt 1
#
no difference than using keyboard to switch to tty1 - auto password entry
Same problem here.
Leap 15 on HP zBook.
With Kernel 4.12.14-lp150.12.25 I have the problem after typeing in the password ad hit enter nothing happens, like described here before. BUT: When you press the enter key constantly then after about 10sec the login is taken along with a lot of enter hits. Everything seems ok on console, but then I tried to install NVIDIA driver with the shell script. And there is the same behavior with the enter key. So you have to choose between 2 options 3 or 4 times. But because the enter hit isn’t taken instantly you have to hit the key a lot of times and then after gaps of about 10 sec the console reacts and is taking the entered key plus all the enter keys, which activating the default setting of the next option.
And with Kernel 4.12.14-lp150.12.28 it’s the same as described here, too.
Hi akarako,
Could you get the issue you described here resolved?
I have a similar issue and could exactly reproduce you problem with kernel version 4.12.14-lp150.12.25-default.
Now, being on kernel version 4.12.14-lp150.12.28-default your problem has been resolved but there is another issue: The login process does not allow for a password entry and the login fails in this way.
You may want to look into my corresponding thread:
Best regards,
Kallistos
Hi akarako,
Could you get the issue you described here resolved?
I have a similar issue and could exactly reproduce you problem with kernel version 4.12.14-lp150.12.25-default.
Now, being on kernel version 4.12.14-lp150.12.28-default your problem has been resolved but there is another issue: The login process does not allow for a password entry and the login fails in this way.
You may want to look into my corresponding thread:
Best regards,
Kallistos
Hello
Similar problem here, Leap 15, desktop PC, kernel 4.12.14-lp150.12.28-default. In every virtual console (1-6), when I type my username at the login prompt, I have no time to enter the password afterwards. Instead a cr/lf it seems to be entered automatically, the password prompt reappears, again a cr/lf it seems to be entered without any action from myself and the **Login incorrect **message is shown, with a reappearance of the welcome message and the login prompt.
My keyboard hwinfo (keyboard is connected via a kvm, but the problem remains even if I connect a ps/2 keyboard directly):
17: USB 00.0: 10800 Keyboard
[Created at usb.122]
Unique ID: LybY.K6PW6TWtOA0
Parent ID: eqBD.Uktxy1IOZI5
SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1:1.0
SysFS BusID: 3-4.1:1.0
Hardware Class: keyboard
Model: “Microsoft Natural Ergonomic Keyboard 4000 V1.0”
Hotplug: USB
Vendor: usb 0x045e “Microsoft Corp.”
Device: usb 0x00db “Natural Ergonomic Keyboard 4000 V1.0”
Revision: “1.73”
Driver: “usbhid”
Driver Modules: “usbhid”
Device File: /dev/input/event1
Device Files: /dev/input/event1, /dev/input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-event-kbd, /dev/input/by-path/pc
i-0000:00:14.0-usb-0:4.1:1.0-event-kbd
Device Number: char 13:65
Speed: 12 Mbps
Module Alias: “usb:v045Ep00DBd0173dc00dsc00dp00ic03isc01ip01in00”
Driver Info #0:
XkbRules: xfree86
XkbModel: pc104
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #15 (Hub)
The strange thing is that with the other desktop pc operated via the same kvm, with leap 15 (same kernel version) as well, but with other hw components (the first is an intel i5 hashwel/internal graphics/gigabyte mb, the second is an amd ryzen 5/nvidia graphics/asus mb), there is no problem to login into the consoles.:\
You could try what I touch on in post #21: boot something else, chroot into 15.0, do zypper ve and zypper up, then reboot to see if the problem clears up. I think that was my solution more than once.
Other times on more than one PC I’ve seen a somewhat similar problem. After logging into a resumed X session, Konsole restarts with login prompts streaming, as can be seen when it first paints less than a full screen of bash prompts and promptly fills up, as if I was holding down the ENTER key, and few other keystrokes can be made to appear as the new prompts are painted.
I can confirm this problem – exactly as you described. Cannot get into any console whatsoever. The auto entering of the password makes it impossible to get in.
Thanks for the suggestion but unfortunately, didn’t solve the problem. I logged into KDE, opened a terminal and executed zypper ve and zypper up. No actions needed to perform. After reboot, the problem persists.
I’ve just noticed another thread about the problem I’m facing:
Yes, and I suggest you try the same solution. Reinstall the 4.12.14-lp150.12.22-default kernel, using the “Versions” tab in Yast Software Management. Put “oldest” in the “multiversion.kernels” in “/etc/zypp/zypp.conf”, as in
multiversion.kernels = oldest,latest,latest-1,running
Then use the “Advanced” menu item during boot to select that kernel. If that fixes your problem, then keep using that kernel until a future kernel update corrects the problem.
Thanks, 
I’ve just followed your advice and the problem disappeared with kernel version 4.12.14-lp150.12.22-default. Now, I’m going to submit a bug report.
I can also confirm that with .25 kernel version the value entered into the Password prompt doesn’t seem to get processed and the cursor waits at the password prompt indefinitely.
Kernel maintainers have asked if anyone has solved this by trying KOTD? Installing kernel 4.20 is easy to do with zypper or yast if you copy http://download.opensuse.org/repositories/Kernel:/HEAD/standard/Kernel:HEAD.repo into /etc/zypp/repos.d/
I came across the very same problem. On a desktop I had this problem initially, but after a reinstall due to a disk that died, the problem has gone away. The desktop system is running kernel 4.12.14-lp150.12.28-default.
Yesterday I upgraded my notebook from 42.3 to leap15 and here the console login problem appeared after the upgrade. Using kernel 4.12.14-lp150.12.22-default the system works fine.
Both systems are running with an encrypted root disk. I also have another leap 15 system at home, that does not have this problem and here the root fs is not encrypted. Perhaps a hint.
Is there anything new to a solution for this problem?
Thanks
Rainer
Last poster I saw ask about failure to be able to login I saw was on Linuxquestions.org a few days ago. He didn’t describe his problem to look the same as posters on this thread, but I think it may have been, even though in Tumbleweed. I suggested he boot the errant kernel in single mode (append S to linux line using e key at Grub menu), login, make some change in YaST user management, then reboot. Maybe the same process would work for the 12.28 kernel in 15.0.
Thanks for your answer. Well my problem is that no matter which account I use even root I get no chance to enter the corresponding password to finish my login. I simply do not get a password prompt instead the login prompt immediately appears again.
I also tried single user mode. In this mode a root console login does work just fine. Strange.
Thanks
Rainer
While in single, did you open YaST and make any kind of change to any user, such as adding one, or changing a password, then try booting and logging in normally?