No invidia graphics, just a laptop with its standard equipment.
I ‘logged out’ my wife on her machine, and when trying to get back, no login prompt appeared. Waited a while & still nothing happened.
I rebooted & that is where the blank screen w/cursor stopped a complete boot.
I remember some time back someone had me add something to the ‘linux’ line in grub edit . (Nouveau?? Maybe don’t remember)
That was probably nomodeset, which is a troubleshooting parameter that doesn’t fix anything, only often enables easier troubleshooting. Other than your laptop has such “standard equipment” as tires, an engine, and probably a transmission, we know nothing about it. Perhaps it would help us to know more about it than Leap is on it? When was it new? Who made it? You should be able to collect that and other troubleshooting information by booting with nomodeset typed on the linu line’s end after striking the E key at the grub menu, then running command sudo inxi -U && inxi -Faz > plaintextfile.txt, followed by copying the content of plaintextfile.txt here between two lines containing only ```. That should give us something to work from.
Did you try booting using any of the “advanced options” in your Grub menu, such as a prior kernel, or recovery mode. What happens when you do?
Possibly there is a troubleshooting file Xorg.0.log in /var/log/ or ~/.local/share/xorg/. If yes, you could use the susepaste command to share it with us.
Do you have any other computers? If you have one you can connect to this laptop via network you may be able to remotely login with ssh to more conveniently collect inxi and other information.
The laptop is maybe 6 yrears old, maube a bit more. It is a Satellite C70(toshiba then). Nope no tires, engines, transmissions of=r the like.
Its graphics are ‘ONBOARD’.
Win 10 boots with graphics.
I did try the advanced (RECOVERY) option, but I didn’t go back to try the older kernel.
My network is in a state of flux now. Changing routers.
I will try the ‘NOMODESET’ in the GRUB linux line, E edit option, and see what happens.
Then I can go from there with the other things you suggest.
But as I did say, it happened after I logged her session out & closing the lid, and it would not come alive, nor give a password prompt.
Yes, I did power down with the power button(after 10 minutes of no response) after I stupidly did the session logout. And I closed the lid at that time. And closed the lid. Hoping it would wake up.
Upon boot after that is when the blank screen w/cursor stayed prevalent.
Tried everything I know(?) to get boot into usable graphics with no good results.
Tried recovery, older kernel(& its recovery).
I put in the install USB tried to boot from disk, nope didn’t work.
Tried an ‘upgrade’ from that USB , & it didn’t work.
Delved into the advanced area in the USB without good results.
SO, WE HAD BACKUPS of her /home directory. And I just did a fresh install, then the backup.
Some cleanup work & it is back to boot par for that machine.
“didn’t work” says nothing. The exact messages from the system would shine some light
Always try to show real output of the system journal, it can also be done from a console by piping through to susepaste: <full_command_here> | susepaste
It will return a URL, copy/paste that here