Description of problem: every time I apply updates if a kernel update is included, grub defaults to the debug kernel. See: # grep -P "submenu|^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f2 Fedora (4.4.6-300.fc23.x86_64+debug) 23 (Workstation Edition) Fedora (4.4.6-300.fc23.x86_64) 23 (Workstation Edition) Fedora (4.4.4-301.fc23.x86_64) 23 (Workstation Edition) Fedora (4.4.3-300.fc23.x86_64) 23 (Workstation Edition) Fedora (4.4.4-301.fc23.x86_64+debug) 23 (Workstation Edition) Fedora (4.4.3-300.fc23.x86_64+debug) 23 (Workstation Edition) Fedora (0-rescue-a80b5fcc380d4d43887e523edaf01db0) 23 (Workstation Edition) Even though: # grub2-editenv list saved_entry=Fedora (4.4.6-300.fc23.x86_64) 23 (Workstation Edition) When I reboot, the highlighted entry is the first entry (4.4.6-300.fc23.x86_64+debug). However, after I run: # grub2-set-default "Fedora (4.4.6-300.fc23.x86_64) 23 (Workstation Edition)" followed by: # grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.6-300.fc23.x86_64 Found initrd image: /boot/initramfs-4.4.6-300.fc23.x86_64.img Found linux image: /boot/vmlinuz-4.4.4-301.fc23.x86_64 Found initrd image: /boot/initramfs-4.4.4-301.fc23.x86_64.img Found linux image: /boot/vmlinuz-4.4.3-300.fc23.x86_64 Found initrd image:/boot/initramfs4.4.3-300.fc23.x86_64.img Found linux image: /boot/vmlinuz-4.4.6-300.fc23.x86_64+debug Found initrd image: /boot/initramfs-4.4.6-300.fc23.x86_64+debug.img Found linux image: /boot/vmlinuz-4.4.4-301.fc23.x86_64+debug Found initrd image: /boot/initramfs-4.4.4-301.fc23.x86_64+debug.img Found linux image: /boot/vmlinuz-4.4.3-300.fc23.x86_64+debug Found initrd image: /boot/initramfs-4.4.3-300.fc23.x86_64+debug.img Found linux image: /boot/vmlinuz-0-rescue-a80b5fcc380d4d43887e523edaf01db0 Found initrd image: /boot/initramfs-0-rescue-a80b5fcc380d4d43887e523edaf01db0.img done Then the system reboots correctly into the desired kernel, until the next kernel errata. I will attempt to erase "kernel-debug-core" to see if this will fix the problem for future releases though the behavior above seems buggy (i.e. when the default kernel is not the debug kernel, then the new kernel installed should not default to the debug version)
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days