I just did it and logged in without stopping the service. Works fine. I just had the locks and it didn’t change plymouth.
I also just noticed that KDE 6.2.4 Wayland f’ed up the widgets. Why are the CPU, RAM, etc. monitor widgets so blurry and faded?
Okay, the point is, if you want to update Plymouth, you should remove the locks and stop the service before proceeding with the update. If you feel safer not updating, then simply leave everything as it is.
2 Likes
Ahh I see what you mean now. Yeah no, I decided to just not update Plymouth.
Same problem here. I did the usual switch to a root console, did zypper dup and stepped away. When I came back, the system appeared to have rebooted itself - the first time I’ve seen that during an update - with the spinner going. Left it for 15 minutes, still spinning, so hit the power button.
The system appears to have come back up properly and appears to be functioning properly. Attempting to run zypper dup again says “nothing to do.”
So what do I need to do to determine whether or not the system is in a clean state?
Well, I just tried that on my second machine. I got this message:
“Failed to stop plymouth-start.servicefirst.service: Unit plymouth-start.servicefirst.service not loaded”
So now what do I do?
OK, on the second machine, I went ahead and did the update. Plymouth did its thing, but apparently that’s irrelevant to the successful finish of the update.
Thanks to the Plymouth maintainers for wasting my entire Thanksgiving afternoon.
When did you use the command? I only stopped the service right before the update and then restarted the machine.
Don’t be upset with people who dedicate their spare time to providing you with software that often improves your life. Bugs happen.
4 Likes
Easy mate. They did screw up the update, but you screwed up the timing. I assumed that today’s update wouldn’t do the same thing as before. We all make mistakes. Nobody’s perfect.
Enjoy your turkey, I’m watching the NFL.
2 Likes
I had all traces of plymouth removed but not locked. Todays update installed and enabled it. Why is plymouth treated like a mandatory package and not the trivial fluff that it is?
Removed and LOCKED and hopefully not 1 more second of my time will be wasted on this clown show.
For me the problem is still the same and has not been resolved by the update.
That worked for me as well.
The update (or, better said, downgrade) didn’t work for me either, with the post-script stuck at 1 percent. However, stopping the Plymouth service using
sudo systemctl stop plymouth-start.servicebefore the update did the trick for me.
This worked for me.
Wish I would have read this before the update today. Did a zypper dup and saw the downgrade so thought ahh they’re fixing it. Then it hung at 4% on my laptop it was some posttrans%actiontek something-or-other and on the server was on posttrans%kernal something-or-other. Same behavior where I was able to ctrl-alt-f3 to get back to my KDE desktop and I had updated my container server (Tumbleweed also) and I did a reboot and all seems well. I was able to connect to a second SSH to my server and reboot it and it came up well too. Wish I knew what in that script didn’t get ran.
Can confirm that …
systemctl stop plymouth-start.service
in advance to …
zypper dup
did the trick.
4 Likes
Thank you ! I did it. I can confirm too. I hope that we can find a more permanent solution to resolve this problem.
Same here, zypper dup on VT4 apparently hung at 4% on a post-trans script (this time a libreoffice-something post-trans) but leaving it enough time to finish as usual (till no-disk-actvity) apparently it did complete even if the VT4 display was still frozen at 4%.
Interestingly VT7 was still active with gdm letting me login and VT2 accepted a root login where I was able to confirm that there was no stuck process and then could reboot as usual after a big upgrade.
On reboot everything looks normal, so apparently plymouth messed up (some) displays but the zypper process completed successfully.
Has it been patched with 20241128?
Why wait? Roll back to a working snapshot, stop Plymouth service, update and you’re done.
1 Like