I’ve went through documentation on start menu and deployments in general. Although I use Aurora, I found that Bazzite has the most extensive documentation.
However, I do not understand how these deployments work with the grub.
Recently, (basically this week) I had some issues with OpenGL or some updates connected I think to GPU Screen Recorder app, whatever. I had an update to many things and it got resolved after reboot.
But today after the latest update Firefox flatpak is kinda broken, buttons missing, crashing, freezing etc.
At first I tried to downgrade via Warehouse (which I gave most permissions via Flatseal) but it was useless as it gave me some errors that Firefox cannot be found/ not installed in the good location whatever.
Then I wanted to roll back, but I got to OpenGL issue again.
So I was thinking if there is a way I can have the system remember 3 (or more) deployments and that they will renew between themselves as time goes by and newer updates come (like a snapshot I guess). Because I have the impression that pinning a specific point in time will make that deployment static.
I was not able to find a similar topic here, hopefully this will help others as well that have this in their mind.
Right, that’s what I had in mind, at least it’s good to know that it has been raised up.
But it also quite worrying that if someone does not make some manual deployments (as I had no idea I would need such) then will only have two of them. And what happens when both are going to be problematic, feels like somebody did not see this one coming.
Of course its a possibility but having two deployments that would both be broken is not something that would happen often. Also it would require something going very badly wrong on the users end.
But computers are computers and everything is always a possibility
Also just to note. Every deployment eats space from the boot partition so it will get filled up pretty quickly if you start pinning multiple deployments.
Usually recommendation is to pin the one right after install and maybe another one once you have setup your system. I usually keep the “after install” one always pinned and might have another one that I sometimes unpinn and pin a newer one. But generally I just run with the one pinned and the two that get refreshed once new images are released.
I have three deployments, and am getting messages that I have 28MB left on my boot partition.
Supporting a longer history would require expansion of /boot proportionally.
