Open DarkGhostHunter opened 1 week ago
You're currently booted onto your :stable
image and not the :latest
one, which is why you still see the old kernel. That's what the dot on the left means, it's the one you're booted into, booting into latest should get you what you need.
Though the fix with the dx-group you need is incoming and these should be done in the next few minutes, when these turn green then I would do the update:
https://github.com/ublue-os/bluefin/actions/runs/11308213011/job/31450808227
I reverted back to stable since latest didn't yield the fsync kernel, that's why you see the (Actual) ostree being stable first and latest second.
I can confirm that installing :latest
does use the fsync kernel, but I didn't bother to rebase to :stable
and see if the kernel remained.
Describe the bug
As title. Rebasing the image should change the kernel, or at least ask to do it somewhere if not.
The kernel stays at
Linux 6.10.7-200.fc40.x86_64
, so rebasing to latest defeats the purpose.What did you expect to happen?
To change the kernel
Output of
rpm-ostree status
Output of
groups
developer wheel
Extra information or context
No response