Do a backup, as you can trash your system.
From the terminal, run rpm-ostree status
.
Here is what mine says:
❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 12h ago
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx-nvidia-open:stable
Digest: sha256:611af780e5c910114dca1491c84c5a508d67f72665f3b4a19c9ca1f840d51d53
Version: 42.20250608.1 (2025-06-08T06:08:47Z)
LayeredPackages: 1password 1password-cli
ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx-nvidia-open:stable
Digest: sha256:611af780e5c910114dca1491c84c5a508d67f72665f3b4a19c9ca1f840d51d53
Version: 42.20250608.1 (2025-06-08T06:08:47Z)
The ● is next to the image that you have booted. In my case, that is 0 (zero), the first one. You are probably booted from the second one, which is 1 (one).
So, you want to ‘pin’ the one that is working. I’m assuming for you it is image 1:
sudo ostree admin pin 1
Then run rpm-ostree status
again, and the image you’re booted from (the one with the ●) should have Pinned: yes
under it. Like this:
● ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx-nvidia-open:stable
Digest: sha256:611af780e5c910114dca1491c84c5a508d67f72665f3b4a19c9ca1f840d51d53
Version: 42.20250608.1 (2025-06-08T06:08:47Z)
LayeredPackages: 1password 1password-cli
Pinned: yes
Assuming all of that worked, and you did a backup, you can tell rpm-ostree to clean up images that you are not booted from:
sudo rpm-ostree cleanup -m
Then you can update again and see how things go.
If you have problems with the update again, and if you have layered packages (like I do, see 1password, and 1password-cli), you might need to remove them before updating. You can use sudo rpm-ostree reset
to remove all layered packages. You will need to add them back once you have a working system.
When everything works for a while, and you decide you don’t need the pinned image, you can unpin it and it will be replaced the next time you update. sudo ostree admin pin -u N
where N is the image’s number when you run the command (later), which you will need to find using rpm-ostree status
.