I am not a KDE/Kinoite user, so I don’t know why Discover doesn’t propose updates, but my guess is that upgrading to a new major release from CLI via rpm-ostree should work the same as for Fedora Silverblue (with the necessary adjustments in repo naming etc).
Thanks, I’ll look into that and try it later when the wife’s not using her laptop, (I put Kinoite on it because she wanted something easy like her old Chromebook.)
Anyway, I should have mentioned in my first post that the obvious approach - updating to the offered Kinoite and hoping that clears the problem - is off the table. I installed Kinoite on Sep 26, and was immediately offered an update. I did that and on reboot, got into a login loop. Further reboots were the same, so I rolled back. The wife said: this one works - leave it alone.
I decided I’d try next when 41 was out, so here we are …
Uh-oh, I see the first step in that Silverblue update procedure is “make sure that you are running the latest update for the current version”.
Not sure why this should be required in an atomic distro, since everything’s being replaced anyway (unless there’s some update to the upgrade code itself).
I may try upgrading to 41 withOUT the update, but I’ll wait a while to see if anyone else has any comments.
But yes, thanks to Mike B for suggesting the rpm-ostree method.
My guess is that Discover notifies about a new major release available based on some config files which indicate such information, and those files are being updated by some package used in the OSTree compose. Given that you’re on an older version of F40, the system probably lacks the information that a new major version is available.
First, I tried the Discover update to a newer version of 40, since I hadn’t tried that again for a month, and perhaps was being offered something different now. Long story short - that gave me the login loop as before. (During the loop, one can see briefly flashing on the screen “Kwin crash reporter” and what appears to be an “automatically report” button.)
Anyway, I then rolled back to my pinned Kinoite 40.
Then, in konsole, I followed the advice from the Silverblue link posted above by Mike B, with the appropriate changes for Kinoite, and SKIPPING the command to update the current version. That did work, and the laptop is now running 41, in spite of this error message:
rpm-ostree transaction failed with:
error: While pulling fedora/41/x86_64/kinoite: While fetching mirrorlist 'https://ostree.fedoraproject.org/mirrorlist': While fetching https://ostree.fedoraproject.org/mirrorlist: [6] Could not resolve hostname
Further, Discover now wants to update Plasma 6, but trying that gives a 404 error. I also get a 404 when I use flatpak update in konsole, so presumably, something is down at the moment.
However the wife has a system that’s working, so she’s happy.
.