Booting to Aurora-DX fails but still falls back
I am having trouble booting my Aurora-DX: stable but it I cannot seem to load stable-20250608.1 or any future or past version. I have tried Latest, 42-20250606, and even on that is matching the current working one 42-20250601.1. Is anyone else having or had an issue booting?
Here is a link to my image. Can someone please take a look and point me in the right direction or what to look for?
Thanks.
https://github.com/CITWil/wil-os/blob/main/recipes/recipe-work.yml
GitHub
wil-os/recipes/recipe-work.yml at main · CITWil/wil-os
Contribute to CITWil/wil-os development by creating an account on GitHub.
Solution:Jump to solution
This will take a while, but I would start by commenting out one module at a time, build, upgrade and see if removing that module fixes the problem
9 Replies
What do you mean you're having trouble booting? What error are you seeing?
It freezes during boot seems to stop responding after stopping a service, but before it load SDDM.
It Immediately seems to be waiting for networking, but it seems to be stuck there awhile, and I cannot hit the esc to see what is going on, but I can push the power button to shutdown
Did you make any changes to your recipe before this started happening?
This might be a problem with some config conflict between your changes and upstream's changes. You can always try rebasing onto the base image instead and see if it still has issues, then you'd know if it's something you changed or something that upstream changed
Nothing recent, It was weeks ago since I updated to DNF in my image. I will try to rebase to the latest ublue image.
Ok seems to be something with my image. I rebased to Ublue Aurora-dx:stable and there was no issue. What area should I look at that can pass the build process but fail the boot process?
Solution
This will take a while, but I would start by commenting out one module at a time, build, upgrade and see if removing that module fixes the problem
If it doesn't, put it back and comment out the next one
If you're removing something in
dnf, take a look in build logs if some crucial component is removed as an dependencyThanks for the help, I will update when I figure it out
Ok so it looks like it was a QT6 update, that and maybe a Java issue.
I was able to narrow it down to a DNF module issue, then started enabling the applications starting with the links and local RPMs but those enabled fine.
So I enabled the other applications in small groups and everything worked until qt6-qtlocation, which dragged a bunch of qt6 updates. Rolled back and removed that one and I was good.
I switched to stable-daily just to test that i was really good and that was successful.
This morning I added the qt6-location and this time it did not have any other qt6 updates. I did some digging and there was a security issue resolved this week with qt6-qtlocation middle of the week.
Thanks @fiftydinar @gmpinder for pointing me in the right direction
Thanks @fiftydinar @gmpinder for pointing me in the right direction
Glad we could help!