It was so nice having a fix before knowing there was an issue, instead of normally having to search for a fix after discovering an issue! I saw the post through Github and checked by running an manual upgrade and sure enough, error due to keys so I ran the fix and problem solved. Thanks Jorge and crew!
I’m enjoying running Aurora-DX-Nvidia, I was messing with Aurora before it officially became part of UBlue so I’m glad it became the KDE version of Bluefin.
Hi, I’ve just executed the command on my Bazzite install on the Legion Go, and after rebooting, all I got it’s a blank screen.
It bootstraps, gets past the Bazzite spinning wheel, and then it remains blank indefinitely.
I’ve already tried rebooting it a couple of times, but it stuck there, never goes past the blank screen.
Is there anything I can do from here to restore it to a functioning OS? Thanks
I saw the announcement on Discord. This seems to have been handled very well. The openess makes me even more comfortable with my choice to move over to Bazzite, more open about a major issue than a number of other systems. Great to see the security in place works properly.
I get the following:
bash: line 1: html: No such file or directory
bash: line 2: syntax error near unexpected token `<’
'ash: line 2: `301 Moved Permanently
Edit: It seems like pasting the command through KDE Connect caused issues some how.
Hi, I’m having some problems with the gaming mode, when I’m on the desktop mode all good, but in gaming mode it stuck at a black screen, I’ve read that in the version bazzite-deck: 40-stable-20240424 works okay with polaris (I have a rx 480), I’ve tried to rebase to that version after applying this fix, but pops this error:
The fix script overwrites the file /etc/pki/containers/ublue-os.pub with the new key and that is why you probably can’t verify the older image. Maybe @j0rge has the old key still laying around somewhere?
You are probably signing your own image already with your own keypair, it’s the SIGNING_SECRET in your github secrets panel in the github settings. Your public key is likely in cosign.pub in the root of your repo.