Bug 1711516 - grub-customizer menu entry list missing linux kernels
Summary: grub-customizer menu entry list missing linux kernels
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub-customizer
Version: 30
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Vasiliy Glazov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1785929 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-18 08:39 UTC by ryan-seymour
Modified: 2023-02-04 13:59 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 18:03:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ryan-seymour 2019-05-18 08:39:04 UTC
Description of problem:
When launching grub-customizer the list of menu entries shows menu entries for my windows 10 install but is missing all fedora kernel entries. This is after a fresh install of Fedora 30 KDE spin.

Version-Release number of selected component (if applicable):
5.1.0-2.fc30

How reproducible:
install and run grub-customizer

Steps to Reproduce:
1. install grub-customizer
2. launch grub-customizer

Actual results:
Missing fedora kernel menu entries.

Expected results:
Show menu entries for fedora kernels.

Additional info:

Comment 1 Carmen F.B 2019-06-16 08:29:42 UTC
The same issue for me :-(

Comment 2 Timor Gruber 2019-08-02 11:56:50 UTC
Hi there, just installed Fedora 30 (GNOME Edition) yesterday - Same behavior as well.
BTW, I'm using a custom grub theme, one that shows an icon for each OS (Fedora included), yet it doesn't show anything at boot time for the Fedora entries (Which do exist fortunately).

Comment 3 Vasiliy Glazov 2019-08-02 12:08:45 UTC
I don't know what to do. Try ask at upstream.

Comment 4 Timor Gruber 2019-08-03 13:40:08 UTC
Hi, some digging revealed that it might has something to do with Fedora's new BLS approach - Take a look at this: https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault

Comment 5 Kévin Selänne 2019-10-24 13:48:25 UTC
Thanks, Timor, for that link. For others coming across this bug and want a quick workaround:

set "GRUB_ENABLE_BLSCFG=false" in /etc/default/grub

to revert to the previous behavior. According to the wiki article, you should also install grubby-deprecated, but in my case it wasn't necessary.

Comment 6 Timor Gruber 2019-10-24 19:09:29 UTC
Kevin this is just great! I confirm it works for me as well, also without the need to install grubby-deprecated.
Thanks so much!

Comment 7 Héctor Louzao 2019-11-02 15:25:44 UTC
could you please add hwinfo as dependency of this package

$ LANG=C grub-customizer                         
localuser:root being added to access control list                                             
 *** initializing (w/o specified bootloader type)…                                            
   * reading partition info…                                                                  
   * Loading Framebuffer resolutions (background process)                                     
   * Finding out if this is a live CD                                                         
sh: hwinfo: command not found                                                                 
 *** initializing (w/ specified bootloader type)…                                             
   * Checking if the config directory is clean                                                
 *** loading configuration                                                                    
 *** loading - preserveConfig: no                                                             

** (grub-customizer:137238): WARNING **: 16:23:00.719: AT-SPI: Could not obtain desktop path or name

   * unsetting saved config
 *** loading settings
 *** loading grub list
   * loading scripts…
   * loading proxies…
   * cleaning up proxy configuration…
   * creating proxifiedScript links & chmodding other files…
   * running grub2-mkconfig

Comment 8 Vasiliy Glazov 2019-11-02 15:48:55 UTC
My upstream bugreport about that ignored.
https://bugs.launchpad.net/grub-customizer/+bug/1670321

Please push upstream to answer.

Comment 9 Vasiliy Glazov 2019-12-23 08:29:14 UTC
*** Bug 1785929 has been marked as a duplicate of this bug. ***

Comment 10 Ben Cotton 2020-04-30 20:37:12 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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.

Comment 11 Ben Cotton 2020-05-26 18:03:32 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.

Comment 12 Nelson Martell 2021-06-24 05:17:17 UTC
I'm having this issue in Fedora 34.

Comment 14 Kevin Adam 2022-01-28 10:08:35 UTC
I'm having the issue as well on Fedora 35. 

Running os-prober results in both boot entries being properly recognized:
/dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager
/dev/nvme1n1p3:Fedora Linux 35 (Workstation Edition):Fedora

But grub-customizer only detects/shows:
Windows Boot Manager (/dev/nvme0n1p1)
UEFI Firmware Settings


Note You need to log in before you can comment on or make changes to this bug.