Actually this would have had some kind of magic if such a change would have helped 
Well I booted into single user and added a new user using yast. After a reboot the console login problem unfortunately was back again. But thanks anyway.
Rainer
That was only one of the symptoms I encountered over time on two older laptops, which differ from a desktop PC with intel processor graphics (on which Leap 15.0 runs well) in that they both have NVIDIA graphics.
On both laptops openSUSE 13.2 and Leap 42.2 / 42.3 worked, openSUSE 13.2 even rock solid without any problem, but on both, since its installation two or three months ago, Leap 15.0 hardly ever worked in a way that I could use it.
During the several installation attempts of Leap 15.0, which on both systems took place using the âDVDâ installer and the four openSUSE repositories only, I followed the suggestion of the installer to not install Mesa-dri-nouveau.
On the one laptop, a Dell Vostro 1720 with NVIDIA GeForce 9600M GS / G96M, two days ago the following happened:
Booting into Leap 15.0 KDE, login for the standard user takes place automatically,
due to the experiences that I gathered, I immediately press Ctrl-Alt-F1 to login as root before anything else,
ha, I get a dead-head replacing my mouse cursor - never saw that before and itâs a pity that I didnât take a photo -,
I pressed Ctrl-Alt-Del, which surprisingly gave me the option to shut down, which I did,
the system ends up with the message that there has been a Kernel BUG due to that the command queue is full.
After that I deleted Leap 15.0 from that Vostro in order to try another clean install, which I however did not after reading through this thread, and the other thread i.e.,
https://forums.opensuse.org/showthread.php/534256-Unable-to-login-to-text-terminals-System-does-not-let-me-enter-password
Symptoms - in general - werenât that dramatic as just described.
The first things that I frequently observed were that KDE became irresponsive after some clicks - no application could be started anymore, no shutdown, login via Ctrl-Alt-F1 then did not work anymore, because I didnât get the password prompt, or it took that long that login was timed out.
Having reached that state I always had to power off the hard way.
The second laptop is a no-name with core i3 and GeForce 310M.
Here I installed Leap 15.0 on a USB stick / key, from which I booted.
That works just fine with another USB stick / key with Leap 42.3 installed on, and Iâm pretty happy that 42.3 is expected to be maintained until the end of June!
On both laptops I had problems to make the updates, so Leap 15.0 on the USB stick still had kernel 4.12.14-lp150.12.22-default, and
therefore doesnât apply.
Symptoms were similar to those on the Vostro.
Except for yesterday:
I boot into Leap 15.0.
I immediately press Ctrl-Alt-F1 to login as root before anything else, which was successful.
In KDE I use the network manager applet to cut the WLAN/WiFi connection (the laptop was connected by cable).
YaST wonât start anymore.
Ctrl-Alt-F1 again, I get to the root prompt there.
Then the following happened (I took a photo of that).
linux-9eg7:~ # shutdown -h now
Failed to connect to bus: No such file or directory
Failed to talk to init daemon.
linux-9eg7:~ #
Power off the hard way again.
This morning I tried to boot the even older kernel 4.12.14-lp150.12.14-default, that was still present on that installation.
Now Leap 15.0 doesnât even boot into KDE anymore.
I get a mouse cursor with the wrong colour along with the startup messages, and thatâs it.
Maybe the last forced power off left its traces.
Iâve just applied kernel update 4.12.14-lp150.12.45-default which solves the problem. As far as I have noticed, console login now works as it is expected.
Iâm glad to hear that. And I hope that fixes the problem for other users, too.
Confirmed from my side!
Great work: Thank you very much to the kernel developers!
Best regards,
Kallistos