How to rollback after an update

Hi,

Please can you help me find the documentation about how to rollback to a previous image.

I am on Aurora latest and updated today. On rebooting the system freezes after i enter my LUKs password. I am able to boot with the previous image in the GRUB menu so can continue to work.

What I can’t figure out is how to remove the latest update completely and attempt the update again.

Can anyone help?

Thanks

1 Like

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.

caveat emptor

Thanks so much. I will give it a try in the morning.

1 Like

Add the -v option to rpm-ostree status and you’ll have the index listed as well:

> rpm-ostree status -v
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: inactive
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx-nvidia-open:stable-daily (index: 0)
1 Like

This just happened to me too, blank screen and freeze at boot. I rolled back, it worked, I performed a system update, and I was back to a broken system… I don’t have layered packages to remove.

Check if the images from today fix it. There was a issue on main that broke the builds.

1 Like

I tried at 6:00 CET this morning, did the new image come out after that time?

Latest image is latest-42.20250612.2 and it was built ~3hours ago.

I’m at work and don’t have access to my machines so can’t verify

20250612.2 not working, sorry

.3 is now up and should finally work

1 Like

Don’t forget you can always rebase to stable.

3 Likes

Thanks for the heads up, just booted on borked 42.200250611.5 downloaded last night. I’m doing a ujust upgrade to get the latest image.

1 Like

BTW, here are the docs; see Updates section. I forgot all about ujust rebase-helper.

Thanks, it’s working.

Thanks, latest-42.20250612.3 is working for me now, but should any new issues arise, I’ll rebase for sure.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.