The update hung. Also it did not finish properly. There was no post snapshot made. Rolled back to pre.
1146 │ pre │ │ Wed 27 Nov 2024 09:31:34 CET │ root │ 12.66 MiB │ number │ zypp(zypper) │ important=yes
1147 │ single │ │ Wed 27 Nov 2024 18:00:42 CET │ root │ 720.00 KiB │ number │ rollback backup of #1103 │ important=yes
1148* │ single │ │ Wed 27 Nov 2024 18:00:42 CET │ root │ 18.71 MiB │ │ writable copy of #1146 │
@dantheman as @Sauerland indicated;
zypper rm libply* ply*
zypper al libply* ply*
dracut -f --regenerate-all
systemctl reboot
I locked the plymouth and libply packages, then reattempted the update. It went through fine this time.
Some more interesting details, likely relevant:
The Plymouth theme named “details” stopped working for me almost four to five days ago; it was just blank. Other themes worked fine. However, hitting “Esc” when these themes showed up would again just give me a blank screen until the system booted.
That is why I tried to reinstall Plymouth in the first place, a couple of days ago and I faced this hang.
Eventually, I had to remove “quiet” and “splash=silent” and add “loglevel=3” to the kernel parameters, which brought similar details to how the “details” theme shows.
Apologies, if these details are not relevant, they appeared to me as if they are.
I would however like to know what I can do if I want to keep Plymouth.
JFYI: The plymouth update at Request 1226800: Submit plymouth - openSUSE Build Service does not solve the issue described here. I hope the crappy plymouth (there are more issues) will be reverted soon.
I used Snapper to roll back and can simply wait a couple of days and update after this is fixed. Snapper is awesome.
Does the 20241126 update fix it?
No it doesn’t contain any fix regarding plymouth, but there is a request to revert it to the last known stable version: Request 1226916: Submit plymouth - openSUSE Build Service
I’ve made workaround using PackageKit upgrade on reboot, these are exact commands I’ve made:
pkcon refresh
pkcon update --only-download
pkcon offline-trigger
and on reboot system will do an upgrade. For me it solved a problem. Its not recommended to use PackageKit instead of Zypper but that is only workaround I’ve found
JFYI: TW20241127 contains the reverted plymouth-22.02.122+94.4bd41a3-12.1.x86_64, which works fine, at least for me.
I’ve just encountered the error from the first post for the second time this week, where the system would switch to the boot screen and zypper dup sat at
=@/.snapshots/1/snapshot
dracut[I]: *** Stripping files ***
dracut[I]: *** Stripping files done ***
dracut[I]: *** Creating image file '/boot/initrd-6.11.8-1-default' ***
dracut[I]: *** Creating initramfs image file '/boot/initrd-6.11.8-1-default' done ***
Skript %posttrans(kernel-firmware-liquidio-20241125-1.1.noarch) wird ausgeführt <5%>===============================================================================================[|]
This is for openSUSE Tumbleweed 20241126-0 -> 20241127-0
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.service before the update did the trick for me.
Didn’t see this before updating two instances of TW KDE today, finding them afterwards with the reboot screen (Plymoth), when pressing ESC had a black screen with blinking cursor.
Pulled the plug/power button and rebooted, went fine in both cases. Afterwards zypper dup shows no packages to install.
Do I need to run anything, any commands? Apparently the installs are doing fine after a hard shutdown and reboot…
Installing that update(downgrade) locked up my system exactly like the last one.
Stopped by here to warn others before I roll back and do the big update again, this time I’ll try sudo systemctl stop plymouth-start.service first.
To others who get stuck: ctrl+alt+del will work, and give you a relatively clean shutdown. Hit it once (don’t spam it/hold it, it’ll force the reboot) and wait a while. It’ll go.
Source: I didn’t do this the first time but reading my logs I realised I just needed to wait longer before I held it, which worked this time.
For 20241127, I’m just gonna use this
and also
zypper al ‘xli’
That did the trick.
Of course, you can always lock packages, but I’m confident the update will work if you disable the Plymouth service first. Just remember to remove the package locks later if you decide to go the route to lock packages.
I did the update and then rolled back using GRUB after discovering this yesterday. Do I really have to disable the Plymouth service for this update?
Not disable, just stop it before the update. It will be started on next boot again.