Don't want to see articles from a certain category? When logged in, go to your User Settings and adjust your feed in the Content Preferences section where you can block tags!
We do often include affiliate links to earn us some pennies. See more here.

Bazzite, the popular version of Linux powered by Fedora and Universal Blue that's great for handhelds including the Steam Deck, ASUS ROG Ally, Lenovo Legion Go and others needs a little manual user effort after a bit of human error.

Unless you take action, you will not get any updates going forward. Developer Jorge O. Castro noted in a forum post how they "were rotating our cosign keypairs this morning, which is the method that we use to sign our images" and unfortunately they "made a critical error which has resulted in forcing you to take manual steps to migrate to our newly signed images".

However, this only affects people who installed Bazzite on a device before July 2nd, if you downloaded it after July 3rd, you're all good.

They have a script set up that you can run that will fix the problem, so all you have to do is run this in a terminal app (code source):

curl -sL https://fix.universal-blue.org/ | sudo bash

To ensure it doesn't ever happen again, they've noted some process changes to be implemented.

See all the details in the forum post announcement.

Article taken from GamingOnLinux.com.
7 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. You can also follow my personal adventures on Bluesky.
See more from me
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
7 comments

I understand this is the easiest way to do that but in general it is a very bad idea to directly pipe any script from curl to sudo bash 😅
Liam Dawe Jul 4
I understand this is the easiest way to do that but in general it is a very bad idea to directly pipe any script from curl to sudo bash 😅
For random scripts across the internet, absolutely. But one directly from the official source? It's fine.
tohur Jul 4
Me making my own image based on Bazzite saved me from this issue lol. cause its my key on github needed for updates not Bazzites haha
I understand this is the easiest way to do that but in general it is a very bad idea to directly pipe any script from curl to sudo bash 😅
For random scripts across the internet, absolutely. But one directly from the official source? It's fine.
Until someone hijacks the domain or the request itself 🙈

(but yes it is probably fine)
Stuff happens, and it is really nice to see a quick response in which:
- Jorge owns up to doing a mistake.
- Provides a resolution.
- Reinforces the current process to avoid it in the future.
- Thanks the rest of the rest of the team.
- Apologizes to the user, and recognizes this erodes trust.

Jorge is a good guy and a responsible leader, please give him another chance.
I understand this is the easiest way to do that but in general it is a very bad idea to directly pipe any script from curl to sudo bash 😅

I looked this up yesterday on their forum & they had alternate instructions for those who might have had issues w/ remote script piping, so there are options.
  • Supporter Plus
Thanks for the heads up!
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register