Hi, this is the second time I experience this issue in a row.
I see there are updates and I install them.
Before the system used to notify if I had to reboot.
Now instead it looks it reboots automatically, but the reboot takes forever. It stays on the Lenovo screen labeled Tumbleweed forever and I have to manually shut down and restart my Lenovo T480s.
You are most likely experiencing the plymouth issue that a lot of people are currently experiencing as well. There is another thread about this: Update hung up on post trans update
tl;dr: plymouth package is broken and it’s the thing causing issues with updates. You have 3 different options to do here:
Stop the plymouth service before updating your system: sudo systemctl stop plymouth-start.service
Remove all plymouth and libply packages from your system and lock them (if you would like to keep plymouth on your system, don’t forget to remove the locks after you update): sudo zypper rm libply* ply* and then sudo zypper al libply* ply*
Wait until the bug is fixed.
(Sorry if formatting is bad. Posting from phone sucks)
I just ran sudo zypper dup a few minutes ago, and my system rebooted and is stuck on the boot splash screen. I did not see when it rebooted as I had gone away to do other things around the house.
Open a VT (by Ctrl+Alt+F4 for instance) and login if the system lets you in, check if the system is running as usual (for instance start ‘top’ and look if the cpu load and processes look normal) then if everything looks ok issue ‘reboot’.
Chances are that just the splash screen is stuck but the system is running ok underneath and next reboot should be normal.
FTR, it was caused by a bug in plymouth package which was introduced together with other issues (like LUKS password problems) and resulted in plymouth services being restarted on update.
Now plymouth has been reverted to the version before this bug so further updates should hopefully be OK … as long as this bug does not creep in again
But of course downgrade (or upgrade) from the version with this bug will still show it once - because bug happens on removal of the affected package version.