+1 to ctrl-alt-fsomething (start at f1 and go up to move through the different virtual terminals). once in a while there are graphics problems which this will fix.
If you’re using GNOME Shell on X you can reload the shell (and all of its extensions) with alt-f2 and then in the “Run a command” dialog that appears type r and hit enter. Unfortunately this doesn’t work in GNOME on Wayland.
If the kernel runs into a oops it can recover and you won’t notice anything except a nasty looking error in dmesg. If it runs into a panic you need to hard reboot the system as it can’t continue to run.
It doesn’t matter what Linux you use. What is your desktop environment?
+1 to ctrl-alt-fsomething (start at f1 and go up to move through the different virtual terminals). once in a while there are graphics problems which this will fix.
If you’re using GNOME Shell on X you can reload the shell (and all of its extensions) with alt-f2 and then in the “Run a command” dialog that appears type
rand hit enter. Unfortunately this doesn’t work in GNOME on Wayland.Thanks Zorin OS uses GNOME apparently
While these can help on other issues, these will do nothing if the driver has an unrecoverable issue.
If the kernel runs into a oops it can recover and you won’t notice anything except a nasty looking error in dmesg. If it runs into a panic you need to hard reboot the system as it can’t continue to run.
And the driver is stuffed if the hardware decides to have an unrecoverable issue.
(I’m looking at you, Intel GuC. You dumb little bastard.)
I agree with Ctrl+Alt+F1/F2 but would add
init 3 init 5
but I learned for my case its better to reboot if my GPU is acting up the instability would eventually come back
the init command probably only works in Debian nowadays givin it’s a thing from the sysvinit era