Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 880124 [details] this is the corrected grub.cfg file which I hand edited to fix problem I simply reversed the kernel order on the machine with a graphics processor so the default works correctly.
OI - my entire note to explain the problem was removed when I added an attachment. 1) when I submitted this bug, bugzilla would not let me get by the "other bugs" like this so I never got to fill in the nice box on stuff. 2) when I hand added an explanation AND added an attachment, my explanation was lost so here we go again. BG: I have two fedora 20 machines - mine has a graphics processor, my wife's does not. I just updated with yum to current releases and rebooted both. My wife's machine worked fine, but mine defaulted to the Rescue kernel. After looking I see that TWO kernels are being added to grub.cfg now: first Rescue, then a normal kernel line. On the NON graphics processor machine, the second kernel is selected by default, BUT ON THE MACHINE WITH A GRAPHICS PROCESSOR THE FIRST KERNEL (RESCUE) IS THE DEFAULT. I fixed the problem on my machine by swapping the order of the kernel lines in grub.cfg. The modified file is attached. It works fine. Since I normally hand edit these files after rebooting and testing, this is no big deal to me but others will find themselves running a Rescue kernel instead of the one intended. I don't know if that hurts, but ...
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.