Steam Deck

14781 readers

422 users here now

A place to discuss and support all things Steam Deck.

Replacement for r/steamdeck_linux.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.

These are not enforced, but they are encouraged.

Rules:

Follow the rules of Sopuli
Posts must be related to the Steam Deck in an obvious way.
No piracy, there are other communities for that.
Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
This is a place of civil discussion, no trolling.
Have fun.

Link to our Matrix Space

founded 3 years ago

MODERATORS

[email protected]

101

PSA: If you use Bazzite on your deck, you need to do a manual fix to get updates (www.gamingonlinux.com)

submitted 4 months ago by [email protected] to c/[email protected]

23 comments fedilink hide all child comments

Bazzite is an alternative OS to SteamOS for the deck and other handheld PCs. Unfortunately due to a mistake, anyone who installed Bazzite before July 3rd 2024 won't get automatic updates.

If this affects you, I'd suggest checking out the article to get instructions on fixing it.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 4 months ago

This is the best summary I could come up with:

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.

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".

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.

The original article contains 189 words, the summary contains 153 words. Saved 19%. I'm a bot and I'm open source!