hello, first post here. this query relates to a new SSD-based install i did recently, using the kde-linux_202605210254.raw file, which was current when i downloaded.
is this raw known by others also to not be able to update?
i began running kde-linux in some qemu vm’s late last year, so i learned then that some of the raws do have such problem, being alpha ofc. otoh, iirc it happened to me with one of those vm’s that the initial raw was ok, but later updates then could not update… this was easy to handle though because all i had to do was boot back into an older boot & proceed.
however now i have no such option, & do not know what to do. these are the konsole messages that have occurred 100% of my many post-install attempts:
[me@kde-linux:~] $ updatectl check
Failed to call CheckNew for ‘host’: Method call timed out
No updates available.
[me@kde-linux:~] $
[me@kde-linux:~] $ updatectl update
host: ✗ Connection timed out
[me@kde-linux:~] [1] $
i know that some users have managed to workaround this by doing `sudo systemctl disable --now kde-linux-sysupdated.socket`, as per KDE Linux not pulling down the latest updates. Verbose output of updatectl update posted - #8 by pg-tips – unfortunately it made no difference for me. after disabling delta-updates that way, i retried the check & update, but nothing changed. i rebooted & again tried, but still no difference. btw post-reboot, this is its status, which tbh confuses me a bit:
[me@kde-linux:~] [1] $ systemctl status kde-linux-sysupdated.socket
○ kde-linux-sysupdated.socket - KDE Linux Update Service
Loaded: loaded (/usr/lib/systemd/system/kde-linux-sysupdated.socket; disabled; preset: enabled)
Active: inactive (dead)
Triggers: ● kde-linux-sysupdated.service
Listen: 127.0.0.1:3129 (Stream)
[me@kde-linux:~] [3] $
given atm my SSD only has a single kde-linux instance [is “snapshot” the proper term?], unless someone can suggest a better alternative, i fear i’ll need to abandon this installation, d/l a newer raw, & begin again… but it would be nice to avoid that.
oh finally, i believe my problem is not a server sync or availability issue, because after doing the delta-updates disable stuff per above, i temporarily rebooted back into my archlinux boot, launched both those aforesaid qemu vm’s, & verified they both easily were able to update to the then-current raw version of today.
thanks in hope of help.
in fact you are correct, but i had not realised the process was still happening, so i stopped watching konsole once i saw what i’d posted above. going back now & relooking, i see my silly error… this is the actual complete transcript:
