Hello everyone! I’ve made a mistake, I didn’t update for a about 5 months and now my system breaks entirely whenever I try to run “zypper dup”. I am currently on version: “20251127” and before starting the update and at the end of it I get no errors. However, after the update I cannot open any program whatsoever and the only way to restart my computer is by typing “sudo reboot” into the console, everything related to the desktop environment is unresponsive. Upon rebooting, I get greeted by this:
This has happened a few weeks earlier too, when I tried to update and figured that I may just have to wait for another update since I thought that I may have gotten a buggy package, however this is not the case, since I still have the same problem a few weeks later.
If you need me to provide any more information or logs, please let me know which one’s you need and how I can find them.
You can boot the updated TW with the previous working kernel, and from there you’ll have a bit of time to create a bug report describing the last working kernel and the kernel crashes on the latest one which appears to be 6.19.11 for you
I need to update again and in the boot menu somehow boot into the previous version of my kernel, what do I do then? What information do I need to provide?
You can change your grub setting to alter the preference. Sometimes in the case of a bad kernel, because sometimes, future updates kernel wise can take time to address your particular problem, I’ll mark the
About kernels I want to save for longer term. Sometimes even just saying preserve last so many isn’t what you want. You want to tell it to preserve an exact version.
Then, I usually use YaST to update the grub to default to that specific version. I just have to remember to undo all of that once the problem has been resolved TW wise.
What I meant was that you’ll have to open a ticket mentioning the last working kernel for your machine along with the specific crash you’re seeing in order to have the issue addressed.
The issue appears to be affecting a small number of users or there’s something specific in your HW configuration that triggers it - which explains why it hasn’t been reported already and fixed.
Booting the distro with an older kernel did not work. So I guess I just should not have waited months to update, so I backed up my home folder and just reinstalled the distro. Everything works perfectly again now. Nonetheless, thanks newsense and cjcox for trying to help.
