atm i seem unable to progress beyond one of the 20260524 builds [iirc it might be 202605240254 - can i view the exact current running version, once i’ve moved past the boot menu & logged in but then forgotten the build timestamp?].
i have tried updates to both 202605280254 [yesterday; Backups; kbackup in kdelinux? - #5 by kdemeoz ] and 202605290254 [within the last hour].
in both cases, after entering my LUKS password, it then dumps me to the rescue screen
is this a known problem for encrypted systems? apparently 202605280254 was fine for non-encrypted systems [ Backups; kbackup in kdelinux? - #9 by pg-tips ]
advice welcomed please.
btw, fwiw, this is tonight’s transcript:
me@kdelinux:~] [1] $ run0 /usr/lib/systemd/systemd-sysupdate update
Discovering installed instances…
Discovering available instances…
⤵ Acquiring manifest file ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS…
Pulling ‘``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS’``.
Downloading 631B for ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS``.
Acquired 631B for ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS``.
Download of ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS`` complete.
Downloading 119B for ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS.gpg``.
Acquired 119B for ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS.gpg``.
Download of ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS.gpg`` complete.
gpg: Signature made Fri 29 May 2026 13:06:05 AEST
gpg: using EDDSA key 15AB3EE61CE450CFED1407BF4121B5F4EAEB53CA
gpg: Good signature from “KDE Linux <linux@kde.org>” [unknown]
gpg: WARNING: Using untrusted key!
Signature verification succeeded.
Operation completed successfully.
Exiting.
⤵ Acquiring manifest file ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS…
Pulling ‘``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS’``.
Downloading 631B for ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS``.
Acquired 631B for ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS``.
Download of ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS`` complete.
Downloading 119B for ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS.gpg``.
Acquired 119B for ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS.gpg``.
Download of ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS.gpg`` complete.
gpg: Signature made Fri 29 May 2026 13:06:05 AEST
gpg: using EDDSA key 15AB3EE61CE450CFED1407BF4121B5F4EAEB53CA
gpg: Good signature from “KDE Linux <linux@kde.org>” [unknown]
gpg: WARNING: Using untrusted key!
Signature verification succeeded.
Operation completed successfully.
Exiting.
Determining installed update sets…
Determining available update sets…
Selected update ‘202605290254’ is already installed, but incomplete. Repairing.
Selected update ‘202605290254’ for install.
Making room for 1 updates…
Found nothing to remove.
⤵ Acquiring ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi`` → /boot/EFI/Linux/kde-linux_202605290254+2-0.efi…
Pulling ‘``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi’``, saving as ‘/boot/EFI/Linux/.sysupdate.partial.kde-linux_202605290254+2-0.efi’.
Downloading 233M for ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi``.
Got 1% of ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi``. 18min 18s left at 215.1K/s.
Got 24% of ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi``. 36s left at 4.7M/s.
Got 48% of ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi``. 13s left at 8.6M/s.
Got 76% of ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi``. 4s left at 12.5M/s.
Acquired 233M for ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi``.
Download of ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi`` complete.
Operation completed successfully.
Exiting.
Successfully acquired ‘``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi’``.
Successfully installed ‘``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605290254.efi’`` (url-file) as ‘/boot/EFI/Linux/kde-linux_202605290254+2-0.efi’ (regular-file).
✨ Successfully installed update ‘202605290254’.
This line is interesting. Did you have a previous failed attempt to install the same update?
well spotted! yes, the initial attempt yesterday failed with the same error at the end as you mentioned in my other thread, except ofc this time with the newer build number. so this time, once that happened, i used the vacuum command you also showed me earlier, which said it deleted one… “something” [sorry i can’t now recall the term it used], waited a while, then repeated the update attempt… which i thought had been successful, but i did not notice that line you’ve pointed out here.
i see now from KDE - Experience Freedom! that there’s a later build, which soon i shall try, albeit i feel pessimistic of success. if this was a mutable system, based on the two last update attempts failing into a boot rescue screen, i would be inspecting my /etc/crypttab file to see if it became corrupted during the update, thus my LUKS partition becoming unable to be accessed during the boot up. however, here in my kdelinux, there simply is no /etc/crypttab file [in my 20260524 build i’m stuck on], so i don’t have the faintest idea how to explain these two failures.
this is rapidly becoming !=fun 
it was looking great, til the end… again.
me@kdelinux:~] $ run0 /usr/lib/systemd/systemd-sysupdate update
Discovering installed instances…
Discovering available instances…
⤵ Acquiring manifest file ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS…``
Pulling '``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS``'.
Downloading 631B for ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS``.
Acquired 631B for ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS``.
Download of ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS`` complete.
Downloading 119B for ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS.gpg``.
Acquired 119B for ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS.gpg``.
Download of ``https://files.kde.org/kde-linux/sysupdate/v2/SHA256SUMS.gpg`` complete.
gpg: Signature made Sat 30 May 2026 13:06:37 AEST
gpg: using EDDSA key 15AB3EE61CE450CFED1407BF4121B5F4EAEB53CA
gpg: Good signature from "KDE Linux <``linux@kde.org``>" [unknown]
gpg: WARNING: Using untrusted key!
Signature verification succeeded.
Operation completed successfully.
Exiting.
⤵ Acquiring manifest file ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS…``
Pulling '``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS``'.
Downloading 631B for ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS``.
Acquired 631B for ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS``.
Download of ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS`` complete.
Downloading 119B for ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS.gpg``.
Acquired 119B for ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS.gpg``.
Download of ``http://localhost:3129/kde-linux/sysupdate/v2/SHA256SUMS.gpg`` complete.
gpg: Signature made Sat 30 May 2026 13:06:37 AEST
gpg: using EDDSA key 15AB3EE61CE450CFED1407BF4121B5F4EAEB53CA
gpg: Good signature from "KDE Linux <``linux@kde.org``>" [unknown]
gpg: WARNING: Using untrusted key!
Signature verification succeeded.
Operation completed successfully.
Exiting.
Determining installed update sets…
Determining available update sets…
Selected update '202605300254' for install.
Making room for 1 updates…
♻ Removing old '/system/kde-linux_202605232010.erofs' (regular-file).
♻ Removing old '/boot/EFI/Linux/kde-linux_202605232010.efi' (regular-file).
Removed 1 instances.
⤵ Acquiring ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605300254_root-x86-64.caibx`` → /system/kde-linux_2
02605300254.erofs.caibx...
Pulling '``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605300254_root-x86-64.caibx``', saving as '/system/.sys
update.partial.kde-linux_202605300254.erofs.caibx'.
Downloading 98.9K for ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605300254_root-x86-64.caibx``.
Got 16% of ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605300254_root-x86-64.caibx``. 58s left at 1.4K/s.
Acquired 98.9K for ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605300254_root-x86-64.caibx``.
Download of ``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605300254_root-x86-64.caibx`` complete.
Operation completed successfully.
Exiting.
Successfully acquired '``https://files.kde.org/kde-linux/sysupdate/v2/kde-linux_202605300254_root-x86-64.caibx``'.
⤵ Acquiring ``http://localhost:3129/kde-linux/sysupdate/v2/kde-linux_202605300254_root-x86-64.erofs`` → /system/kde-linux_2
02605300254.erofs...
Pulling '``http://localhost:3129/kde-linux/sysupdate/v2/kde-linux_202605300254_root-x86-64.erofs``', saving as '/system/.sys
update.partial.kde-linux_202605300254.erofs'.
Transfer failed: Timeout was reached
Failed to retrieve image file.
Exiting.
(sd-pull-raw) failed with exit status 1: Input/output error
…and so, again i ran…
me@kdelinux:~] $ updatectl vacuum
Deleted 1 instance(s) of host.
i shan’t try again, for that build, so shall await more new build/s tomorrow 
tonight managed to update to 202606010254& so am marking this thread closed / solved, due to my Do these network transcripts look ok, or problematic? - #8 by kdemeoz