https://bugs.kde.org/show_bug.cgi?id=522286
--- Comment #3 from [email protected] --- Additional Information for KDE Team: AFFECTED VERSIONS: - 202606260254 (initial report) - 202606270310 (confirmed panic) - 202606280806 (confirmed panic - latest) ISSUE SCOPE: - Not download/corruption related (verified via SHA256 checksum match) - Not isolated to single image version - Pattern suggests systemic boot-time initialization failure REPRODUCTION: 1. Download/stage new image (sysupdate or manual curl) 2. Verify integrity (SHA256 checksum matches SHA256SUMS) 3. Reboot system 4. Kernel panic occurs ~1-2% into kernel initialization KERNEL PANIC BACKTRACE (consistent across all three versions): - plymouth(main+0x1694) - libc.so.6(__libc_start_main+0x89) - plymouthd(_start+0x25) - /usr/lib/libc.so.6 symbol resolution failures STABLE VERSION: - 202606240257: Boots successfully, used as pinned workaround ENVIRONMENT: - KDE Linux on QEMU/KVM VM - systemd-boot (systemd 260.2-2-arch) - systemd-stub with UKI support - TPM2 enabled, Secure Boot disabled MANUAL WORKAROUND (verified working): - Pin to 202606240257 via /etc/systemd/sysupdate.d/kde-linux.conf with MinVersion constraint - Cleanup script provided for maintenance DIAGNOSTIC NOTES: - Manual curl --continue-at - download works (resume-capable) - .erofs and .efi files integrity verified post-download - systemd-boot configuration valid - Issue reproducible on every boot attempt of affected images ROOT CAUSE HYPOTHESIS: Boot-time initialization in Plymouth/systemd-stub layer, not image content or download mechanism. Possibly: missing kernel module, incorrect initramfs, or systemd configuration regression introduced in these versions. REQUESTS: 1. Compare 202606240257 vs 202606260254 build configurations 2. Check systemd-stub/Plymouth changes between versions 3. Verify initramfs generation for affected versions 4. Consider alternative boot splash backend (breeze vs moonlight) -- You are receiving this mail because: You are watching all bug changes.
