Well a few of us just rebased to 40 today so far no one said anything
Well a few of us just rebased to 40 today so far no one said anything
K@Niklas 
Do you have an SVG of your logo and a screenshot you like in particular?
Do you have an SVG of your logo and a screenshot you like in particular?
Jyeah we're either safe or it's some subtle bug lol
Mwell they said fail to boot due to bootloader having bad shim....
FHmm, Timothée says that just having bootupd is not enough
https://github.com/fedora-silverblue/issue-tracker/issues/543#issuecomment-2045629776
https://github.com/fedora-silverblue/issue-tracker/issues/543#issuecomment-2045629776
GitHub
Describe the bug Trying to rebase an existing SB39 to SB40 fails to boot showing vmlinuz-6.8.1-300.fc40.x86.x64 has invalid signature. you need to load the kernel first on an Thinkpad T495. I was n...
FFor people that don't have the issue like me, they probably don't use Secure Boot
Fif someone uses Secure Boot & he updated successfully to 6.8 kernel, than great ig
Ball 6 of the machines I manage have SecureBoot enabled, upgraded to 6.8.4 and had no problem
Bstill very odd that they are treating the issue as common and general, yet our users seem to be untouched
NI'm gonna send you the logo over real quick, sec
NI redesigned it a bit
MThat absolutely needs to be the logo for the menu and in all of the fedora locations
Nthe final v1 version, i used the same color for the stars
aurora_v1_logo.svg43.74KB
Nalso made in illustrator and inkscape
Nalso screenshot coming soon, once I rebased to the new image from the ublue-repo 
@Kyle Gospo
@Kyle GospoNI have some ideas
NI want to make an austronaut wear a slightly hidden aurora badge maybe the default wallpaper 
NLmao, the idea with the austronaut came in my head when I redid the logo
Nwould def be funny
S@j0rge about the
omz install script, do you need the part where it installs/uninstalls zsh too? I have second thoughts about it. I don't need that part since my image has zsh, so I'm not sure if I should offer to install zsh as a layered package, or just return an error if zsh isn't installed and you try to install omz
Jmaybe echo that you should run the chsh command ahead of time? Both bazzite and bluefin have it so no worries there
SI was about to say you don't need to chsh ahead of time because omz proposes it post install. But as I understand you want to use this in a UI so that's gonna be an issue ^^' I could pipe 
yeschsh Jdo we know if the omz chsh works on silverblue systems?
SIt should work, I'll test just to be sure
SIt only prompts it if
zsh is not your login shellJyeah there's been cases where we have to say "the tool will give you instructions at the end, ignore them"
SOh! There's a way to skip it
SGitHub
A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, pyth...
A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, pyth...SIs
$CHSH is set to no it just won't trySSo I suppose it could just ignore that part, so users can use the toggle to install/uninstall
omz, and chsh has to be done with ujustI think we should get the negativo Nvidia repo in before we ship F40 as latest so we're not switching drive packages mid-cycle
DUsers might not even notice but there could be minor behavioral differences
Jare you aware of the amount of work that takes?
DHonestly, no.
DIs it a matter of adding a new repo to akmods instead of rpmfusion and then switching the package name and providing a valid nvidia.conf file? And updating downstream builds to use it?
DI know negativo is already used for codecs/multimedia
DMaybe I'll give it a try later to see what it takes
DNot trying to minimize the amount of work it takes at all
BGitHub
Since we use differing kernels from upstream, we should be properly setting the ostree.linux label on the image to reflect the actual kernel within the image.
BI started a PR... but haven't had much time, and forgot that
https://github.com/ublue-os/akmods/pull/167
podman pull is not docker pull so things aren't quite what I'd hoped forhttps://github.com/ublue-os/akmods/pull/167
Kjust expanded your scope sry
Bexplain pls?
KGitHub
Since we use differing kernels from upstream, we should be properly setting the ostree.linux label on the image to reflect the actual kernel within the image.
Bi see
Bi replied
KI'll make an issue in main 
DMain adds the rpmfusion repo in install.sh right? And then that gets used to install Nvidia in hwe?
DSo we need to add negativo17's Nvidia repo in hwe since that one isn't in main ,right?
BFirst thing i thought of is the Space Force. So I guess you're doing it right?
DIs my understanding correct that something like this would be what we need for the negativo17 driver? https://github.com/ublue-os/hwe/pull/229
MTake a look at ucore, Bazzite, and bluefin. Each uses the repo for some items. You'll see what we mean that it's a little bit more complicated than just pulling in the repo
