https://bugs.kde.org/show_bug.cgi?id=522286
--- Comment #6 from [email protected] --- NEW FINDINGS — Problem is not image content, but systemd-sysupdate itself: TEST SETUP: - New VM booted from current ISO (kde-linux_202607040653) - ISO boot works cleanly (no panic) - System runs stably on 202607040653 FINDINGS: 1. systemd-sysupdate check-new: WORKS - Shows candidates correctly (202607040303, 202607031422, etc.) - Downloads succeed - Signatures verify OK 2. systemd-sysupdate acquire 202607040303: PARTIALLY WORKS - Download successful - End of process: "failed with exit status 1: Input/output error" - Version not finalized/activated 3. systemd-sysupdate list: CRASH - Command crashes with: "Code should not be reached at src/sysupdate/sysupdate-update-set-flags.c:158, function update_set_flags_to_string(). Aborting." - Also affects pending queries ROOT CAUSE: Not image, but systemd-sysupdate tool itself - ISO boot (202607040653) = OK - sysupdate tool = BUG in code (update_set_flags_to_string crash) HYPOTHESIS: - ISO-compatible images since 202606260254 work when booted from ISO - But sysupdate integration has a separate bug - Old VMs with sysupdate-based updates → panic (combined effect) - New VMs from ISO → boot OK, but sysupdate tool crashes during update process VERIFIED WORKAROUND: - Mask systemd-sysupdate.timer - Activate new images only manually after ISO testing - Wait for sysupdate fix REQUESTS: 1. Check: sysupdate-update-set-flags.c:158 (function update_set_flags_to_string) 2. Is this a known bug in current systemd version? 3. ISO-compatible images alone are not at fault — sysupdate integration is the problem -- You are receiving this mail because: You are watching all bug changes.
