Bug 1119785 - after install boots directly to windows [NEEDINFO]
Summary: after install boots directly to windows
Alias: None
Product: Fedora
Classification: Fedora
Component: efibootmgr
Version: 20
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-15 13:48 UTC by sean darcy
Modified: 2015-06-29 21:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-29 21:35:53 UTC
pjones: needinfo? (seandarcy2)

Attachments (Terms of Use)

Description sean darcy 2014-07-15 13:48:19 UTC
Description of problem:

New HP laptop, W 8.1, EFI boot. Installed F20 from Xfce Live. No errors on install.

The laptop boot directly to windows. I need to hit ESC and f9, I get:

- OS Boot Manager
 - Fedora 20 [HDD SERIAL NUMBER]
 - Boot from EFI file

When I choose Fedora, I get the grub2 manager, which includes a choice for windows.

F10 in the gives me boot options, but only for devices.
Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

efibootmgr -v
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 2001,0000,3000,0002,0003,2002,2003
Boot0000* Windows Boot Manager HD(2,c8800,82000,b75fbdf8-d691-411e-8c4d-bc2e5b5e8898)File(\EFI\Microsoft\Boot\bootmgfw.efi)(invalid optional data length)
*** Error in `efibootmgr': double free or corruption (out): 0x00007fff63e991e0 ***
======= Backtrace: =========
======= Memory map: ========
Boot0001* USB Hard Drive (UEFI) - Generic Flash DiskAborted

Comment 1 Peter Jones 2014-10-20 19:12:57 UTC
Can you see if this is still a problem with the following updates applied:



Comment 2 Fedora End Of Life 2015-05-29 12:22:36 UTC
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.

Comment 3 Fedora End Of Life 2015-06-29 21:35:53 UTC
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

Thank you for reporting this bug and we are sorry it could not be fixed.

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