Ra section about "if you haven't updated yet, do this instead:" would let users proactively fix it
Rinstead of waiting for breakage
Jpeople already reported the breakage
EPR is up for main. I think posting Kyle's message makes the most sense considering it's currently a well reported issue
E
Kadded extra line at end
BHi, I want to customize flatpak configuration of my image and replace the fedora repos with flathub, I believe that this configuration is not a part of the ostree image and that it should be configured with a tool like yafti, but I am not sure about that
BWhat is the best way to do this?
Kfedora ships flathub now
Kthis was needed prior to F40
Bit does but it shipis both user and system and it has to be enabled by the switch
Bthey also add the fedora repos
KWe customize the flatpak repos via hardware/user setup scripts
Kboth are systemd services
BI want to just have one user flathub repo and nothing else
BCan you link me the services please?
KGitHub
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. - ublue-os/bazzite
KGitHub
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. - ublue-os/bazzite
BI'll look into these, thanks
BI don't know why I make so many typos, probably because it's a bit late
Rdo you mind doing a click on hwe for a rebuild
Rjust so all the images are good on latest
KDone
Rthanks
Rone question is, will this affect ucore at some point down the line? I assume it would
Rprobably good to do it well in advance now that we know what the fix is
J@Kyle Gospo back
JUniversal Blue
Yeah we’re going to see if we can fix this without having to do all that, hang tight if you can or just stay on yesterday’s image.
Jwhat am I saying here
Jsorry, I'm slow and sauced rn lol
Jhung out with an old oss friend, described his action usage, we're so small still lol
KYou can just say it's fixed, and to ensure they have our akmod secure boot key enrolled
FShould the MOK screen be requested always now instead of in UEFI only in isogenerator?
Fnvm, it's all good
MUefi is the only thing with secureboot
MMy question is how did this not trigger when F40 was released?
Ahow did this happen? there are no breaking changes with 6.9
Adid fedora really change the signing key?
MThat's what's confusing for me. There were reports that something like this happened for regular silverblue installs during F40 beta but we never got hit
Ayeah because ublue has a custom signing key
ETrying to understand more of it but the gist is the shim for grub needed to be updated but SB doesn't currently do that. Why it needed to be updated isn't clear to me
Abut from what i understand fedora cant update grub or the shim
Aso they must have cycled the signing key
EPossibly. I'll link the issue if you all want to dig with me
Ai looked through it
Acant understand what happened
EYeah, I've read through most of it. Causation isn't so clear: https://github.com/fedora-silverblue/issue-tracker/issues/543
EAnd... Why now and not 3 months ago? What was shielding us?
Aso the shim contains the singing keys the kernel is allowed to use
Aold shim = not new keys
