Description of problem: I wanted to change the boot order in order to start on Windows 7 for default on a laptop configuration (XP2 M1330) which is still under F19. All updates have been made before trying to change the boot sequence. How reproducible: always Steps to Reproduce: 1. I followed this process: https://flyingpengwin.wordpress.com/2011/12/15/fedora-how-to-change-the-boot-order-in-grub2-to-windows-7/ 2. Meaning: $ su - # cat /boot/grub2/grub.cfg |grep Windows # grub2-set-default "Windows 7 (loader) (sur /dev/sda1)" # grub2-mkconfig -o /boot/grub2/grub.cfg Actual results: AS I said in title, my setup is in French which lead to "sur" instead of "on" within the boot line sequence. $ echo $LANG fr_FR.utf8 After rebooting what I observe is no changes so it still starts on the first line. Expected results: Booting on Windows as default instead of Fedora. Additional info: I found a fix for this, which is before running any command in root, I export LANG=C. Then I set the boot sequence as wanted to "Windows 7 (loader) (on /dev/sda1)". This is strictly a localization issue. Hope a fix can be found easily.
Please try again, this time make sure you run mkconfig before grepping.
Bug still present event with making the mkconfig before grepping.
(In reply to Fabien Archambault from comment #2) > Bug still present event with making the mkconfig before grepping. The output from the grep must however have been different.
After updating today I still have this annoying issue! [root@localhost ~]# export LANG=C [root@localhost ~]# grub2-set-default 'Windows 7 (loader) (on /dev/sda1)' [root@localhost ~]# grub2-editenv list saved_entry=Windows 7 (loader) (on /dev/sda1) [root@localhost ~]# grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.13.7-200.fc20.i686+PAE Found initrd image: /boot/initramfs-3.13.7-200.fc20.i686+PAE.img Found linux image: /boot/vmlinuz-3.13.7-200.fc20.i686 Found initrd image: /boot/initramfs-3.13.7-200.fc20.i686.img Found linux image: /boot/vmlinuz-3.12.10-300.fc20.i686+PAE Found initrd image: /boot/initramfs-3.12.10-300.fc20.i686+PAE.img Found linux image: /boot/vmlinuz-3.12.10-300.fc20.i686 Found initrd image: /boot/initramfs-3.12.10-300.fc20.i686.img Found linux image: /boot/vmlinuz-0-rescue-81daeb8fed525e786633000ab4273ce8 Found initrd image: /boot/initramfs-0-rescue-81daeb8fed525e786633000ab4273ce8.img Found Windows 7 (loader) on /dev/sda1 done [root@localhost ~]# grep Windows /boot/grub2/grub.cfg menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-92004C09004BF331' {
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.
Bump to F21 as I still have the issue after upgrading the kernel!
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.