I have rebased to Fedora 42 Pre-release but now I cannot go back. If I execute the rebase command to the Kinoite branch, everything is downloaded and I get asked to reboot, but then the version 41 is not there to select from at boot.
Does anybody know what is going on?
Thank you!
Would you please post the output of the rpm-ostree status command from the latest working properly booted deployment?
Additionally, if you can successfully boot to F42, you can try rollback, i.e. rpm-ostree rollback to your previous deployment. It is also recommended to pin your current working deployment, i.e. sudo ostree admin pin 0 before the rollback command.
State: idle
Deployments:
â—Ź fedora:fedora/42/x86_64/kinoite
Version: 42.20250218.n.0 (2025-02-18T07:53:37Z)
BaseCommit: c3dd1a90815dc654d11ebb03c8d2766fbbd134ed1688d1cc0a9d62a45a1ac94f
GPGSignature: Valid signature by B0F4950458F69E1150C6C5EDC8AC4916105EF944
LayeredPackages: syncthing
fedora:fedora/42/x86_64/kinoite
Version: 42.20250219.n.0 (2025-02-19T07:54:03Z)
BaseCommit: 96ce6dab7046772f92e5ca07a75f8ba961b7db5a4a2f351302b9936d39335f70
GPGSignature: Valid signature by B0F4950458F69E1150C6C5EDC8AC4916105EF944
LayeredPackages: syncthing
As you can see, I already updated a couple of times F42, so the F41 deployment is no longer available to roll back to.
USB audio and recognition of certain types of flash drives broke in 19.n.0 so I rolled back to 18.n.0.
Thank you for any ideas.
I can of course reinstall with F41, but that’s more work…
Upstream software can usually handle data/configuration migration forward (upgrade) but not backward (downgrade). For this reason, it is usually safer to rebase from e.g. F41 → F42, but less safe to go the other way.
Also, I’m not sure what LayeredPackages: syncthing indicates, but it looks like there is something not quite right with both deployments.
So it seems like you don’t have a really stable working deployment, and since you can at least boot successfully, I would suggest backing up your important data and reinstalling the system. Although it will probably cost more effort, I think this is the safest and cleanest way, rather than trying to rebase back to F41.
As I already mentioned, If you decide to rebase, make sure to pin your current deployment, so you don’t accidentaly lose it (by default, only the two most recent deployments are kept).
syncthing is a package for peer to peer syncing I use. I’ve layered it because it didn’t seem to work as flatpak.
I will backup data and reinstall the system, it seems like the safest option.
Thank you for your help !
I didn’t know that syncthing is a package.
F42 is not even officially available as a beta, so some instability is expected.
If your system is generally working and you really don’t want to bother with reinstalling, I can try to reproduce the issue, but I won’t be able to do it until Sunday.
Yes, I made a mistake rebasing to F42.
I already reinstalled the system: pc is brand new and the install was one week old.
The reason I rebased is that in MS Edge flatpak (used for work reasons only) the browser can’t seem to find my webcam. Difficult conducting Teams meetings like this.
In F42 this worked, strangely enough. I hope it starts working on F41 too, so I do not have to use Win 11 to telework…
Thanks again for your efforts !
There’s a bit more to this, but in general you can relatively harmlessly rollback to any previous deployment, which is not the case with rebasing to an older version. So, again, just pin your current deployment if you are trying a new, even stable, version.
FWIW, I also layer Syncthing in F41 Silverblue and Kinoite, and it works well
Great tip, thank you, will keep that in mind for sure.
To be fair, it is in the beta freeze period, so it’s like one month out from the beta being released, so I doubt it’s very unstable.
@jverl Since you can’t rollback and you can’t rebase to F41, if it’s running fine, I would just leave it. The beta is released next month anyways, and the actual release is in 2 months.
There is Syncthingy Flatpak which works without issues.
You can absolutely try beta stuff
sudo ostree admin pin 0rpm-ostree status rpm-ostree rollback NUMBER the number starts with 0 (top)