Hi,
I recently updated my TW. The update broke my sleep screen as well as wifi (having to troubleshoot via phone) I tried to rollback via snapper which made things worse (terminal wont appear) so then i tried to boot in recovery mode and Im stuck on this screen.
Any guidance on a solution would be greatly appreciated!
Thank you,
Erik
Going to need some information about your system before anyone can start to help.
Could you describe how the rollback was done? From the read-only grub snapshots?
Did it complete successfully and you rebooted back to find the terminal not starting?
It would be helpful to get some information on your system, like which DE you’re using and the output of:
inxi -Faz
Pavin,
I wouldnt even be able to run that command. Like I mentioned that is the screen Im getting. It doesnt move past this. Second when I could access my desktop, I couldnt even pull up a terminal, so I wouldn’t be able to run that command. The rollback was performed: yast2 snapper → original installation → (forgot the term as im recalling this from personal memory.
-Erik
@OceanJasper if you hit the enter key a few times (after the additional log output obscuring the login prompt) do you get a prompt to enter rescue mode after entering your system root password.
Hi Malcom,
Hitting the enter key allowed me to run Pavins solution. I think I am currently in recovery mode.
-Erik
Could you boot into one of the read-only snapshots from the grub (bootloader) menu?
If you find yourself in a snapshot that’s not working, reboot into an older one until you find one that’s working as expected (preferably with an older 6.7.x series kernel). Then from the read-only snapshot, open up a terminal and do:
sudo snapper rollback
systemctl reboot
This should solve the broken update.
Android _Gynous,
What would you like to know? How can I get the information youre looking for?
-Erik
Erik, your problem appears to be an update that didn’t quite finish correctly. You’re missing key libraries.
The screenshot from which the rollback is run looks like a broken snapshot, you would need to go back in time to find a snapshot that works. Booting into the working snapshot you would be greeted with a functional desktop and not the console TTY, that’s how you know the snapshot is good. 
Here’s the detailed steps:
Basically the stuff pavinjoseph had already asked here:
It would be helpful to get some information on your system, like which DE you’re using and the output of:
They already seemed to have been able to narrow down the issue.
My next question would have been to ask if you had installed any new packages. Specifically any before your last zypper dup and restart.
I once installed a package made for Intel that was incompatible with my machine, which also caused something similar to your situation. The solution was to boot in to a working snapshot and rollback from there. It was then I was able to work my way backwards, tracing it to the offending package.
If it was just a broken upgrade, doing a sudo snapper rollback should resolve the issue. However, if it happens a second time there may be another issue preventing the update from completing.
Let’s hope it was just a one-off mishap during a dup. 
Android_Gynous,
I appreciate it. I think Ill have to back up my files and do a new os install. I dont have any working snapshots 
thanks for getting back!
-Erik
Pavin,
Ill try that documentation, thank you but the snapshots I have are not working :/. Thanks for helping me out with this!
-Erik
Here’s the link to the latest documentation on performing system rollback:
Just to test, find the earliest snapshot and try to boot from it and rollback.
Also from the snapshot, provide the output of:
sudo snapper list
If systemctl reboot or shutdown -r now isn’t working from the snapshot due to missing libs, do:
# run as root
sync
echo u > /proc/sysrq-trigger
sleep 10
echo b > /proc/sysrq-trigger
Im curious if this has anything to do with it
Pavin,
Meant to update you. That last snippet seemed to work. If you don’t mind (have the time) , how did you come up with this solution?
Thank you,
Erik
Meaning what? Did you successfully roll back to 20240321 or something like that? Did you since try zypper dup once or more to get current with latest 20240414?
Glad it worked out in the end 
I’m still concerned though as rolling back to such a snapshot (from which you couldn’t run systemctl reboot) would still be missing key shared libraries.
If you were referring to this part, this is the proc interface to magic sysrq and reisub:
https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html
Yeah i just did an update and now it wont boot into the GUI and I cant roll back, its saying that there isnt enough disk space. Ill upload a pic of the screen soon.