Bug ID | 1222069 |
---|---|
Summary | Systemd-boot issue after upgrade |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | x86-64 |
OS | SUSE Other |
Status | NEW |
Severity | Critical |
Priority | P5 - None |
Component | MicroOS |
Assignee | forgotten_u0-bnvADNc@user.net |
Reporter | regis@hubelia.com |
QA Contact | qa-bugs@suse.de |
Target Milestone | --- |
Found By | --- |
Blocker | --- |
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36 Build Identifier: Boot/System config: systemd-boot with encrypted root Last known working version: 7.6.1 After doing a transactional-update dup, we get the following error: /init: error while loading shared libraries: libsystemd-core-255.so: cannot open shared object file: No such file or directory Very similar, if not exactly the same issue as https://bbs.archlinux.org/viewtopic.php?pid=2158970 We use MicroOS on 2 Framework 13th Gen laptops, a i9 9900k desktop, and 2x 13900k desktops. The latest upgrades works fine on the 2 13900k desktops, but the same error occurs on the 9900k and the 2 Framework laptops. Unfortunatly, we do not have bios upgrades for the Framework laptops or the 9900k, we are using the most recent bios on all computers. Reproducible: Always Steps to Reproduce: 1. boot version 7.6.1 - works perfectly 2. run "transacitonal-update dup" and reboot Actual Results: the boot loader is interupted with the above error message and a kernel panic (see the arch linux link for a screenshot, we have the same on our side) Expected Results: The system should boot as usual