| Summary: | drakboot crashed when switching to GRUB2 (grub2-install: error: will not proceed with blocklists) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | François Agrech <f.agrech> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | minor | ||
| Priority: | Normal | CC: | belof.ilya, marja11, ouaurelien, thierry.vignaud |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakxtools | CVE: | |
| Status comment: | |||
|
Description
François Agrech
2017-07-22 11:50:18 CEST
Thanks for the report, François. This issue has already been reported before, but don't worry, your report helps to know how many users are affected by this issue. *** This bug has been marked as a duplicate of bug 20023 *** Resolution:
(none) =>
DUPLICATE
Thierry Vignaud
2017-09-18 15:34:23 CEST
CC:
(none) =>
thierry.vignaud The issue is that when one switches from grub-legacy to grub2 on a non UEFI system[1], the list of boot devices is filtered for generic bootloader needs by bootloader::allowed_boot_parts() but we don't know yet that the user will later switch to grub2 However grub2 has more restrictions... See: http://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm#n713 But as the switch to grub2 is done _after_, we got bit... We could add a later check: if grub2 has been selected, we could popup with an error message. Aka rerunning bootloader::allowed_boot_parts() and making sure the choosen boot_device is part the new list. Status:
REOPENED =>
ASSIGNED Hi Thierry, Does it still valid in mga7 and Cauldron? This message is a reminder that Mageia 6 is end of life. Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL) within 3 weeks from 2020-08-05. 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 Mageia version prior to Mageia 6's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot be able to fix it before Mageia 6 was end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad CC:
(none) =>
ouaurelien Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
ASSIGNED =>
RESOLVED |