Hi everyone, This plymouth update is for almost sure causing some issues for luks enabled boot drives too. See here if it is interesting for you: https://forums.opensuse.org/t/new-opensuse-update-won-t-let-me-get-pass-thro... And here too: https://www.reddit.com/r/openSUSE_Slowroll/comments/1gzpj3g/luks_broken_afte... Many say that they can't reproduce the error. However I experienced too, and thankfully I have a Timeshift Snapshot in place to revert. I have a busy week but I'll try to detail the next step to reproduce it if I can this weekend. Kindest regards On Wed, 27 Nov 2024 at 19:30, Frank Krüger via openSUSE Factory < factory@lists.opensuse.org> wrote:
Am 27.11.24 um 09:52 schrieb Thomas Zimmermann via openSUSE Factory:
Hi
Am 27.11.24 um 09:41 schrieb Axel Braun:
Am Dienstag, 26. November 2024, 22:25:01 Mitteleuropäische Normalzeit schrieb Knurpht-openSUSE:
Op dinsdag 26 november 2024 22:00:45 Midden-Europese standaardtijd schreef Frank Krüger via openSUSE Factory:
Hi there,
Today's update using 'zypper dup' immediately reboots and the machine hangs "forever" (AMD Ryzen 7 PRO, KDE Plasma 6.2.3 with Wayland). Seems to be related to the posttrans(dracut-059+suse.665.gd2af7028-1.1.x86_64) script.
Anyone else seeing this? Any idea? Thx.
Regards, Frank Yep, saw that just now Same here - had to return to previous snapshot 20241118
@Dimstar - any update in the pipeline?
There's a plymouth update pending that hopefully resolves the crash during startup.
This plymouth update does not solve the issue described here at all. Could you please revert the crappy plymouth? Thx.
Regards, Frank