Bug 1367185 - 30-prober disables multiboot
Summary: 30-prober disables multiboot
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 25
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-15 19:37 UTC by ernie_07
Modified: 2017-12-12 10:26 UTC (History)
3 users (show)

Fixed In Version: Fedora 25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:26:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ernie_07 2016-08-15 19:37:21 UTC
Description of problem:

Installing Fedora 24 or 23 causes ONLY the recently installed OS to be bootable.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Install Fedora-24 or Fedora-23 on a system containing at least one working Linux OS.
2.Boot after installation has completed.



Actual results:
1.ONLY the recently installed OS will be bootable.
2.Other installed Linux OS's that were working will not be bootable.

Expected results:
1.ALL installed OS's should be bootable.

Additional info:


## NEW Begins _ Debug Line ( machine="" ) commented out
###	machine=""
tmp_machine=""
tmp_machine="$machine"
tmp_string=""
tmp_string="$(printf '\nVALUE of machine BEFORE IF = : %s :\n	\n' "$tmp_machine")"
printf "$tmp_string"
if [ -z "$machine" ] ; then
  machine="$(uname -m)"
  printf '\nVALUE of machine WITHIN IF = : %s :\n	\n' "$machine"
fi
## NEW Ends


The snippet above both demonstrates the problem and a potential solution. Execute grub2-mkconfig saving the output to a file. Search for VALUE and the uninitialized state of variable machine will become apparent.

NOTE, the tabs between the newlines withing the IF were required to keep final newline from being swallowed. This may be a cosmetic bug.

Comment 1 ernie_07 2016-11-24 08:24:33 UTC
Problem had NOT been fixed. file "/etc/grub.d/30_osprober" in Fedora 25 (64 bit) Workstation is IDENTICAL to "/etc/grub.d/30_osprober" in Fedora 24 (64 bit) Workstation. Rendering existing systems unbootable is NOT acceptable!

Comment 2 ernie_07 2016-12-09 09:31:18 UTC
A DNF Upgrade fixed this problem.

Filesize, modification date and time for the file in /etc/grub.d follow:

12083 Dec  1 14:30 30_os-prober

Comment 3 Fedora End Of Life 2017-11-16 14:04:37 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 4 Fedora End Of Life 2017-12-12 10:26:21 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.


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