`sudo mokutil --import secure_boot.der` should be `public_key.der`, just fixed this in bluefin docs
sudo mokutil --import secure_boot.der should be public_key.der, just fixed this in bluefin docs after someone reported it
Joh actually lemme just recommend
RYeah, that would be best. I'm away for an hour, so will make those updates a little later
Junderstood
EI reported it, https://github.com/ublue-os/bluefin-docs/issues/19
secure_boot.der is still in the Bluefin repo, bluefin-docs is OK
secure_boot.der is still in the Bluefin repo, bluefin-docs is OK
GitHub
NI think it looks great other than the change Jorge asked to make.
Alike the variants and the readme overall
AThe base COSMIC image is intended to be a starting point for users to build their own custom images.I do not like this line as it implies that this image is not ready to use as is
Acan you reword it a bit to say you can use it as is and if not
Awhats missing?
Jthat's the right wording for a base image
Atheres no -main in the name though
Ayou mean bazzite-cosmic would build from this?
Aie whats missing for this image to be used by end users?
NI wouldn't think Bazzite would build from this specific repo. I believe Fedora plans to support Cosmic as an official image at some point.
N@Kyle Gospo can correct me if I'm wrong on that.
Ayeah but by that point wheres the clout
NI'd rather not have an alpha desktop experience be one of the experiences user associate with Bazzite.
Athats a fair point
Abut circling back to the discussion of the image, what is missing?
Nthat I'm not sure on 
I'll let others weigh in on that.
I'll let others weigh in on that.J@Noel I think you can commit my suggestion in the PR?
Aalso, is there a reason you wouldnt be able to rebase to cosmic and back to kde?
Noh yeah, sure can.
Joh so do that and let's get the one more +1 then merge it
Nsounds good, just commited your change.
Jhttps://github.com/ublue-os/bluefin/pull/1586/files I need a hand reviewing with someone who understands libvirt/selinux
RThere's some context and brief discussion here
https://discord.com/channels/1072614816579063828/1087140903031943178/1271552858034147469
https://discord.com/channels/1072614816579063828/1087140903031943178/1271552858034147469
EWhy does it trigger restorecon twice?
KGitHub
Can be restored to extra when build issues are fixed
K^ there's your skew
Nyay!
EShould we force it?
KI'll look and see if i2c-piixbuf has been updated
Kand update that in akmods copr
Kthen it'll succeed
EAwesome 
KGitHub
Opposite of previous PR, merge me when this module is fixed upstream (Build will succeed).
Moved from common to extra.
Moved from common to extra.
G
G
GHelp please
GI can't see any logs as to what exactly is failing in the github build job.
Aprobably better to post in #
custom-image-support , also oot you got fortinet working in atomic fedora?
custom-image-support , also oot you got fortinet working in atomic fedora?
RFortnite? Or is fortinet something else
PI just want to say that yesterday Bluefin pulled update, I'm now on 560 NVIDIA drivers on an old Pascal, seems like all is working fine.
PThanks for the hard work. 
Aits a vpn
GI also got a post in #custom-image-support
custom-image-supportRoh lol mb
GI tried adding the repo to /etc/yum.repos.d/ and just doing rpm-ostree install forticlient
Gbut got the same error
