Description of problem: akmod is designed to compile modules at boot time. After installing a new kernel and/or a out of tree module update(presumed), it starts compiling e.g. nvidia module, taking a full 2 minutes on a 4 year old mid-tier laptop. All of this goes by without providing any user feedback. The user might think the system has frozen, so they will reset the system on repeat until the compilation manages to complete by force of luck. There should be better integration with the graphical boot process, just like we have with system updates, to show some kind of progress indicator or even a simple wait spinner with a description like _"completing system update of x component"_. It cannot be expected that every user knows to press ESC to look at the console output, where they perhaps might notice the running akmods job. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. akmods running on boot time, e.g. after kernel and/or module update and fresh boots Actual results: Notice how the boot process stalls without any feedback on the boot screen, unlike when running pre-boot system updates 3. Optionally press ESC to see an indication of akmods running Expected results: Graphical user feedback to the likings of a pre-boot system update Additional info:
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.