Bazzite switches deployments on cold boot even with updates disabled and a pinned deployment
Hi! I’m having a strange issue with deployments on Bazzite.
I disabled AutomaticUpdates and pinned the deployment that works correctly for my hardware.
rpm-ostree status confirms that updates are disabled and the older deployment is pinned.
If I reboot, the correct pinned deployment loads.
But when I fully power off the laptop and turn it back on, Bazzite boots into an entirely different deployment that wasn’t even listed before.
This happens even though I did not rebase, unpin, or enable updates.
Here is what I see now:
The pinned deployment: stable@sha256:e217ce...
The unexpected deployment that appears after a cold boot: stable@sha256:e5a392...
Is this expected behavior?
Why is Bazzite generating or switching to another deployment even though updates are disabled and a pinned deployment exists?
What is the correct way to stay permanently on a specific build without the system switching deployments?
Thanks in advance!
I disabled AutomaticUpdates and pinned the deployment that works correctly for my hardware.
rpm-ostree status confirms that updates are disabled and the older deployment is pinned.
If I reboot, the correct pinned deployment loads.
But when I fully power off the laptop and turn it back on, Bazzite boots into an entirely different deployment that wasn’t even listed before.
This happens even though I did not rebase, unpin, or enable updates.
Here is what I see now:
The pinned deployment: stable@sha256:e217ce...
The unexpected deployment that appears after a cold boot: stable@sha256:e5a392...
Is this expected behavior?
Why is Bazzite generating or switching to another deployment even though updates are disabled and a pinned deployment exists?
What is the correct way to stay permanently on a specific build without the system switching deployments?
Thanks in advance!
