Bug 16058 - Mageia puts itself first in the BootOrder list, there is no easy way to override that during install
Summary: Mageia puts itself first in the BootOrder list, there is no easy way to overr...
Status: RESOLVED DUPLICATE of bug 15583
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL: https://lh3.googleusercontent.com/-V5...
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-05-30 01:10 CEST by Bill Jr
Modified: 2015-06-01 19:09 CEST (History)
5 users (show)

See Also:
Source RPM: grub2
CVE:
Status comment:


Attachments
Report of the Mageia 5 installation (152.44 KB, application/x-xz)
2015-05-30 10:58 CEST, papoteur
Details
report.bug.xz (152.22 KB, application/x-xz)
2015-05-31 04:53 CEST, Bill Jr
Details

Description Bill Jr 2015-05-30 01:10:21 CEST
Description of problem:
I have an distro installed in my notebook (with uefi support), and when i try to install Mageia 5 RC, i select in resume to install Grub in mageia root partition, because i want to keep grub bootloader from my first distro. But Mageia overwrite this grub install, and when i reboot, i can't start my first distro installed. Mageia install grub in MBR, but i dont select to do this.
This problem does not occur in Mageia beta 3

Version-Release number of selected component (if applicable):
Mageia 5 RC with Grub2

How reproducible:
Every time...i try install in 2 different notebooks, and try too in Virtualbox, with legacy and uefi support.

Steps to Reproduce:
1.Install first distro
2.Install mageia 5 rc and select to install grub in mageia root partition(ex. /dev/sda5)
3.reboot to start first distro, and see the error.


Reproducible: 

Steps to Reproduce:
Comment 1 Bill Jr 2015-05-30 05:43:48 CEST
An additional info: I use the classical Mageia 5 RC DVD 64bits (a 3.6gb iso file)
Comment 2 Manuel Hiebel 2015-05-30 09:21:45 CEST
Thanks for the bug report.
Could you provide the file /root/drakx/report.bug.xz as an attachment ?

Keywords: (none) => NEEDINFO

Comment 3 papoteur 2015-05-30 10:57:11 CEST
Here I see the same.
Installing with 5-final-round 3, DVD x86_64 on UEFI system.
Choosing bootloader from summary.
Ask for installation in sdax, (/ of the new installation).
The Mageia 4 system has no more bootloader to configure.
Restart Mageia 5
Go to MCC, configure the bootloader. It is in /dev/sda.

CC: (none) => yves.brungard_mageia

Comment 4 papoteur 2015-05-30 10:58:10 CEST
Created attachment 6668 [details]
Report of the Mageia 5 installation
Comment 5 Manuel Hiebel 2015-05-30 12:08:02 CEST
********************************************************************************
* grub2: install.sh
********************************************************************************
grub2-install

should be grub2-install --grub-setup=/bin/true /dev/sdaX no ?

Keywords: NEEDINFO => (none)
Priority: Normal => release_blocker
Assignee: bugsquad => thierry.vignaud

Comment 6 Thierry Vignaud 2015-05-30 18:41:22 CEST
We do that on !UEFI case.
Here it's UEFI and on Barry request, we only run grub2-install.

Barry?

BTW, nothing is broken, so that cannot be a release blocker

Priority: release_blocker => Normal
CC: (none) => zen25000
Severity: major => normal

Comment 8 Thierry Vignaud 2015-05-30 19:05:37 CEST
AFAIC on UEFI, distros (really grub2) just depose their minimal image in the ESP.
Here the issue is that mga4 & mga5 maybe used the same name?
Anyway UEFI was not officially supported with mga4 whereas it's now for mga5
Comment 9 Manuel Hiebel 2015-05-30 19:26:22 CEST
ah yes sorry didn't read carefully code
Comment 10 Thierry Vignaud 2015-05-30 20:12:16 CEST
Indeed grub2 generates EFI/mageia/grubx64.efi which would be the same name for all Mageia releases.
So grub2 only overwrite a previous Mageia grub2, not another OS.
I wonder what does other distros, if their grub2 payload is versioned or not?

Summary: Grub overwrite original bootloader installed in dualboot => Grub overwrite original Mageia bootloader installed in dualboot
Source RPM: (none) => grub2

Samuel Verschelde 2015-05-30 20:20:49 CEST

Whiteboard: (none) => FOR_ERRATA

Comment 11 Marja Van Waes 2015-05-30 23:49:13 CEST
Did this report get hijacked?

The original reporter, Bill Jr, did not say his first install was a Mageia install, but 

> i select in resume to install Grub in mageia root partition, because i want to
> keep grub bootloader from my first distro.

@ Bill Jr

If your "first distro" is *not* Mageia, then please tell us and attach your /root/drakx/report.bug.xz from your Mageia install on an efi system

And also attach the output of (as root)

efibootmgr

However, if your "first distro" is Mageia, then there is no need to do anything :-)

CC: (none) => marja11

Comment 12 Bill Jr 2015-05-31 04:53:37 CEST
Created attachment 6669 [details]
report.bug.xz

file from my mageia 5 rc install
Comment 13 Bill Jr 2015-05-31 04:57:57 CEST
Hi Marja!
You are right...mageia 4 is not my first distro installed.
I also try dualboot with mageia 5 rc with Debian, manjaro, arch and fedora, and i have the same error.

In Mageia 5 resume install, i choose grub install in /dev/sda4, and, when mageia show me the distros/entries founded, i see my first distro, set as linux, in /dev/sda1, its OK, but, when i restart and see the bootsplash mageia, and grub selection, my first distro is in /dev/sda2...a wrong place.

Sorry about my english Marja!
best regards
Bill Jr (a.k.a. spylinux)
Comment 14 Thierry Vignaud 2015-05-31 06:56:37 CEST
First you tested an old install (16.86 whereas we're now at 16.102).

Secondly, the grub.cfg matches fdisk output: your first distro is on on sda2. sda1 is the ESP, it doesn't contain an OS.
AFAIC Mageia's grub.cfg is OK.

As your system is UEFI and your disk is partitioned as GPT, we did,'t alter MBR as there's no MBR.
On such system, grub2 can only install itself in the ESP, so he added an entry on the ESP as EFI/mageia/grubx64.efi
Unless you formatted your ESP, it should still contain both Manjaro grub2 & Mageia grub2.
As that's what every distro does and as we cannot do much about that in UEFI mode, that's not a bug.
We could maybe hide the bootloader location under UEFI as we cannot alter what grub2-install will do anyway...

Attaching the output of the efibootmgr (as requested) would be helpful...
Depending on your machine UEFI firmware, it should either display a menu or boot the default grub2.

So I don't understand what's you exact issue? You should be able to start your other distro from Mageia's grub2 menu

Keywords: (none) => NEEDINFO

Comment 15 papoteur 2015-05-31 13:50:32 CEST
Added in errata:
'With UEFI system, we will install Grub2 without any choice. The bootloader will be installed in the ESP partition (Bug [https://bugs.mageia.org/show_bug.cgi?id=16058 16058]). There is no more reference to MBR.'

Whiteboard: FOR_ERRATA => IN_ERRATA

Comment 16 Samuel Verschelde 2015-05-31 15:42:44 CEST
(In reply to papoteur from comment #15)
> Added in errata:
> 'With UEFI system, we will install Grub2 without any choice. The bootloader
> will be installed in the ESP partition (Bug
> [https://bugs.mageia.org/show_bug.cgi?id=16058 16058]). There is no more
> reference to MBR.'

We need to understand what the issue is before writing in the Errata. The entry you added is at most a Release Notes information, not an Errata entry (it doesn't describe a bug).

Whiteboard: IN_ERRATA => FOR_ERRATA

Comment 17 Bill Jr 2015-05-31 17:09:05 CEST
Sorry, i cannot explain correctly, i install mageia in Uefi mode, with GPT, not MBR.
And i mark mageia to install grub in /dev/sda4, your root partition, not overrite my first distro grub install.

With this...when i try to load my first distro from mageia grub, i have the Kernel panic error...
Comment 18 Bill Jr 2015-05-31 17:10:47 CEST
I think this is an issue, or a bug...i dont know, because if i select to Not install mageia grub in first partition, why they do this?

I try the same thing in my notebook with legacy mode, and have the same problem.
Samuel Verschelde 2015-05-31 18:55:13 CEST

Keywords: NEEDINFO => (none)

Comment 19 Thierry Vignaud 2015-05-31 21:39:54 CEST
@stormi: please stop removing the NEEDINFO keyword

(In reply to Bill Jr from comment #17)
> And i mark mageia to install grub in /dev/sda4, your root partition, not
> overrite my first distro grub install.

We didn't overwrite it.
Eeach distro writes a different grub2 image in the ESP:
- Mageia: EFI/mageia/grubx64.efi
- Fedora: EFI/fedora/grubx64.efi
- Suse: EFI/opensuse/grubx64.efi
- ...
(or shim.efi if not using grub2)

Again, please attach the output of the efibootmgr command in order to see what's available.
 
> With this...when i try to load my first distro from mageia grub, i have the
> Kernel panic error...

That just mean os-prober wrongly guessed the parameters for your other distro.
It probably picked the wrong initrd:
        initrd /boot/intel-ucode.img
You can use the "e" keyboard in order to alter the grub2 entry

Keywords: (none) => NEEDINFO

Comment 20 Samuel Verschelde 2015-05-31 21:54:45 CEST
(In reply to Thierry Vignaud from comment #19)
> @stormi: please stop removing the NEEDINFO keyword
> 

Well, there are so many "NEEDINFO" bugs that actually got their answers in our bugzilla database that I'll probably not stop when I think the user gave relevant information that allows to go further (I was wrong here). I'll try to avoid doing it for your bugs.
Comment 21 Thierry Vignaud 2015-06-01 09:22:39 CEST
You can continue to do it but here there's a answered request for info for quite some time...
Comment 22 Marja Van Waes 2015-06-01 15:08:21 CEST
Removing "FOR_ERRATA" 

It can still be re-added when we have more information and decide there's an issue that needs to be listed in the Errata.

@ Bill

running (as root) 

  efibootmgr 

(so _without_ any options after "efibootmgr")

*cannot* break anything.

Whiteboard: FOR_ERRATA => (none)

Comment 23 Geraldo Witeze Junior 2015-06-01 16:09:48 CEST
Hello all! I think we have a problem of communication. For @Bill it's hard to write in English, so I'm trying to help him. Please, have in mind the English is not my first nor second language, so if you don't understand what I'm trying to say, please ask me.

I'm waiting @Bill give us the return of "efibootmgr" command. He had to remove Mageia 5 RC because he needs to work using his computer, so he will make another test in a virtual machine to give us the information asked. But he said that the problem is the following: it's not possible just don't install grub 2. He tested with several distros pre-installed (Debian, Fedora, Manjaro and Arch) using the classical install DVD. He just wants do not install the Mageia 5 grub 2 because he already has a grub 2. So, the question is: why it's not possible do not install the grub 2 in Mageia 5 RC installation? As he says, using the other distros mentioned it's possible do not install the grub 2 and just keep the grub 2 already installed, only in Mageia 5 RC installation process this is not possible. 

Other information: in a previous release (Beta 3) it was possible to keep the old grub installation saying for Mageia to install the grub on his own / partition. Doing this the previous grub was preserved. But on RC this solution doesn't work. 

If you want to see @Bill original description in portuguese, look here: http://mageiadobrasil.com.br/forum/viewtopic.php?f=5&t=996&start=30

If you need more information, please ask me and I will try to get it. Sorry for my poor English, I'm just trying to help.

CC: (none) => woitze

Comment 24 Marja Van Waes 2015-06-01 16:22:26 CEST
@ Geraldo

Thanks for your help :-)

@ Thierry

When seeing the summary screen in installer
http://doc.mageia.org/installer/5/en/content/images/dx2-summary.png
all of Mageia has been installed, except the bootloader, correct?

So, if someone does really *not* want a Mageia bootloader added (or a former Mageia bootloader overwritten) on the ESP, he can then:

* switch to tty2
* remove the DVD or USB-key he installs from
* reboot with Ctrl + Alt + Delete
* and then update the bootloader in his other distro (or in the older Mageia install) to find the newly installed Mageia.

Is that correct?
Comment 25 Thierry Vignaud 2015-06-01 16:30:24 CEST
That could work but that would bypass updates & the like and the installation isn't bootable as it (need to rely on some other distro to use grub2 & to have os-prober & to run update-grub).
AFAIC other distro don't offer the choice to not install grub2 on UEFI AFAIC...
Geraldo Witeze Junior 2015-06-01 16:30:50 CEST

Summary: Grub overwrite original Mageia bootloader installed in dualboot => In dualboot Mageia Grub overwrites original bootloader from other distro installed before.

Comment 26 Marja Van Waes 2015-06-01 16:44:10 CEST
@ Geraldo

For UEFI-installs, " In dualboot Mageia Grub overwrites original bootloader from other distro installed before." is not true.

Mageia only adds its own bootloader to the ESP and doesn't touch any bootloaders from other distros.

However, Mageia puts itself first in the BootOrder list

With efibootmgr, it is possible to put a different bootloader first in the BootOrder list, and then use that bootloader.

Summary: In dualboot Mageia Grub overwrites original bootloader from other distro installed before. => Mageia puts itself first in the BootOrder list, there is no easy way to overrride that during install

Comment 27 Marja Van Waes 2015-06-01 16:46:55 CEST
@ Geraldo

Thx for having changed it, anyway.
I wouldn't have noticed that the old summary didn't match Bill's problem, either ;-)

Summary: Mageia puts itself first in the BootOrder list, there is no easy way to overrride that during install => Mageia puts itself first in the BootOrder list, there is no easy way to override that during install

Comment 28 Geraldo Witeze Junior 2015-06-01 16:50:36 CEST
(In reply to Marja van Waes from comment #27)
> @ Geraldo
> 
> Thx for having changed it, anyway.
> I wouldn't have noticed that the old summary didn't match Bill's problem,
> either ;-)

@ Marja, I just changed the title for clarify that the old installation wasn't Mageia, as some people here thought. But your title is better indeed. 

Thanks!
Comment 29 Marja Van Waes 2015-06-01 17:24:17 CEST
(In reply to Marja van Waes from comment #26)

> 
> With efibootmgr, it is possible to put a different bootloader first in the
> BootOrder list, and then use that bootloader.

For instance as follows:

# efibootmgr
(That will show something like:)
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0002,0003
Boot0001* mageia
Boot0002* linux
Boot0003* Windows Boot Manager

Here, the boot entry for linux is "Boot0002", to put it first, first delete the current BootOrder with

# efibootmgr -O

and then create a new BootOrder with the linux bootloader in the first place, e.g.: 

# efibootmgr -o 0002,0001,0003
In the output, you'll see a line with the new BootOrder:
   BootOrder: 0002,0001,0003
so the "linux" bootloader will be used next time you boot your system)

Of course, "0002" must be changed to the real number of the manjaro bootloader entry in the efibootmgr list
Comment 30 Geraldo Witeze Junior 2015-06-01 18:10:22 CEST
Well, let's go again!

I asked @Bill for some information and I think it's useful.

1) His HD was partitioned as follows:
--/dev/sda1 mount /boot/efi
--/dev/sda2 mount / (root)
--/dev/sda3 mount /home
--/dev/sda4 mount swap
--/dev/sda5 / (root Mageia)
--/dev/sda6 /home (mageia)

The distro installed on sda2 was Manjaro, but he also tried with Fedora 21 and 22, Arch and Debian.

What's the problem? In the end of Mageia 5 RC installation process there is the option to choose where to install the grub (he chose /dev/sda5 or the root Mageia partition). But in fact this option doesn't exists, because grub always will be installed on /dev/sda1. So the installer offers a false options which confuses the user. If it's not possible to install the grub on the root partition, why there is such option? 

Isn't possible to remove this option? Is it possible to have the option of don't install the grub anywhere? 

When @Bill chose to install Mageia 5 RC grub2 on /dev/sda5 he couldn't boot his first distro. Ok, we don't know exactly why, but we know that doing the same with Fedora and Manjaro (installing the grub on root partition) doesn't result in the error produced by Mageia 5 RC installer. 

I hope it's clear now. 

Thanks!
Comment 31 macxi 2015-06-01 18:26:19 CEST
I did tests with the installation of Mageia 5RC in virtualbox. 
My tests are only in virtualbox, so don't know how much apply to a real machine.

I installed the Mageia 5 RC DVD 64bit in virtualbox with EFI enabled. Mageia 5RC started with Grub2. Installed correctly in the sda2 partition and the user name was "mageia5".

Then I installed Mageia 5 RC in the same virtual machine, in the partition sda4, with Grub2 boot menu in the root partition / (sda4). The user name "mageia5-rc".

Once installed, I rebooted the virtual machine and the menu (grub2) installed was the "mageia5-rc" (sda4). The second installation of Mageia 5RC subscribed MBR, despite the setting to be installed at the root partition / (sda4).

Another mistake went after I close the virtual machine. When I tried again to access the boot menu. I could not. It appeared a terminal with shell 2.0.

See the sequence of screenchots:
https://picasaweb.google.com/106373477520489204423/Mageia5RCDVDClassico64bitUEFIErro

https://picasaweb.google.com/106373477520489204423/Mageia5RCDVDClassico64bitEFIErro2

Then I did another test with the installation of Ubuntu 1404.
I used the virtual machine I did in virtualbox, with both instaled Mageia 5RC an in sda2 and sda4 in another.

I installed Ubuntu 1404 on partition sda2. I installed the Boot menu in the root / sda2. The result was the same with the Mageia 5RC. Ubuntu 1404 subscribed what was in the MBR and installed its menu, with access to 5RC Mageia which was in sda4.

I shut the virtual machine. Then I tried to access the boot menu, but appeared a terminal with Shell 2.0, Repeating the same mistake occurred with the Mageia 5 RC

See the sequence of screenshots on Picasa gallery: Ubuntu 1404 UEFI error:
https://picasaweb.google.com/106373477520489204423/Ubuntu1404ErroUefi

CC: (none) => terraagua

Comment 32 Barry Jackson 2015-06-01 18:42:32 CEST
(In reply to Geraldo  Witeze Junior from comment #30)
> Well, let's go again!
> 
> I asked @Bill for some information and I think it's useful.
> 
> 1) His HD was partitioned as follows:
> --/dev/sda1 mount /boot/efi
> --/dev/sda2 mount / (root)
> --/dev/sda3 mount /home
> --/dev/sda4 mount swap
> --/dev/sda5 / (root Mageia)
> --/dev/sda6 /home (mageia)
> 
> The distro installed on sda2 was Manjaro, but he also tried with Fedora 21
> and 22, Arch and Debian.
> 
> What's the problem? In the end of Mageia 5 RC installation process there is
> the option to choose where to install the grub (he chose /dev/sda5 or the
> root Mageia partition). But in fact this option doesn't exists, because grub
> always will be installed on /dev/sda1. So the installer offers a false
> options which confuses the user. If it's not possible to install the grub on
> the root partition, why there is such option? 
> 
Because this is a knon bug:
https://bugs.mageia.org/show_bug.cgi?id=15583

> Isn't possible to remove this option? Is it possible to have the option of
> don't install the grub anywhere?

Believe me I tried - see above bug report

> 
> When @Bill chose to install Mageia 5 RC grub2 on /dev/sda5 he couldn't boot
> his first distro. Ok, we don't know exactly why, but we know that doing the
> same with Fedora and Manjaro (installing the grub on root partition) doesn't
> result in the error produced by Mageia 5 RC installer. 
> 
> I hope it's clear now. 
> 
> Thanks!

I'm guessing that this is a duplicate of https://bugs.mageia.org/show_bug.cgi?id=15583 then?
Comment 33 Geraldo Witeze Junior 2015-06-01 18:44:11 CEST
Other useful information provided by @Bill:

Both Manjaro and Fedora offer the option of don't install the grub2 on /dev/sda (which is /dev/sda1). When we unmark the option "install grub2 on /dev/sda" on both distros the installer puts the grub2 on / (the root partition, not /dev/sda1) under the folder /root/boot/, creates the folders needed (efi, extlinux and grub2), generates the files except "grub.cfg" and doesn't activate the grub2. Just the files are there, with no activity or interference.

After this @Bill just updated the older grub2 of his 1st distro and everything works! It's not possible with Mageia.

Thanks for the help and the patience.
Comment 34 Barry Jackson 2015-06-01 18:49:23 CEST
(In reply to macxi macxi from comment #31)
> I did tests with the installation of Mageia 5RC in virtualbox. 
> My tests are only in virtualbox, so don't know how much apply to a real
> machine.
> 
> I installed the Mageia 5 RC DVD 64bit in virtualbox with EFI enabled. Mageia
> 5RC started with Grub2. Installed correctly in the sda2 partition and the
> user name was "mageia5".
> 
> Then I installed Mageia 5 RC in the same virtual machine, in the partition
> sda4, with Grub2 boot menu in the root partition / (sda4). The user name
> "mageia5-rc".
> 
> Once installed, I rebooted the virtual machine and the menu (grub2)
> installed was the "mageia5-rc" (sda4). The second installation of Mageia 5RC
> subscribed MBR, despite the setting to be installed at the root partition /
> (sda4).
> 
> Another mistake went after I close the virtual machine. When I tried again
> to access the boot menu. I could not. It appeared a terminal with shell 2.0.
> 
> See the sequence of screenchots:
> https://picasaweb.google.com/106373477520489204423/
> Mageia5RCDVDClassico64bitUEFIErro
> 
> https://picasaweb.google.com/106373477520489204423/
> Mageia5RCDVDClassico64bitEFIErro2
> 
> Then I did another test with the installation of Ubuntu 1404.
> I used the virtual machine I did in virtualbox, with both instaled Mageia
> 5RC an in sda2 and sda4 in another.
> 
> I installed Ubuntu 1404 on partition sda2. I installed the Boot menu in the
> root / sda2. The result was the same with the Mageia 5RC. Ubuntu 1404
> subscribed what was in the MBR and installed its menu, with access to 5RC
> Mageia which was in sda4.
> 
> I shut the virtual machine. Then I tried to access the boot menu, but
> appeared a terminal with Shell 2.0, Repeating the same mistake occurred with
> the Mageia 5 RC
> 
> See the sequence of screenshots on Picasa gallery: Ubuntu 1404 UEFI error:
> https://picasaweb.google.com/106373477520489204423/Ubuntu1404ErroUefi

I think that you are being confused by current limitations of the UEFI firmware in VirtualBox. The VBox nvram is lost between VBox sessions, so you need to manually boot as noted here:
https://wiki.mageia.org/en/EFI:_can_no_longer_boot_into_Mageia#Boot_Drops_to_UEFI_Shell_.28in_VirtualBox.29
Comment 35 Geraldo Witeze Junior 2015-06-01 18:53:33 CEST
(In reply to Barry Jackson from comment #32)
> (In reply to Geraldo  Witeze Junior from comment #30)
> > Well, let's go again!
> > 
> > I asked @Bill for some information and I think it's useful.
> > 
> > 1) His HD was partitioned as follows:
> > --/dev/sda1 mount /boot/efi
> > --/dev/sda2 mount / (root)
> > --/dev/sda3 mount /home
> > --/dev/sda4 mount swap
> > --/dev/sda5 / (root Mageia)
> > --/dev/sda6 /home (mageia)
> > 
> > The distro installed on sda2 was Manjaro, but he also tried with Fedora 21
> > and 22, Arch and Debian.
> > 
> > What's the problem? In the end of Mageia 5 RC installation process there is
> > the option to choose where to install the grub (he chose /dev/sda5 or the
> > root Mageia partition). But in fact this option doesn't exists, because grub
> > always will be installed on /dev/sda1. So the installer offers a false
> > options which confuses the user. If it's not possible to install the grub on
> > the root partition, why there is such option? 
> > 
> Because this is a knon bug:
> https://bugs.mageia.org/show_bug.cgi?id=15583
> 
> > Isn't possible to remove this option? Is it possible to have the option of
> > don't install the grub anywhere?
> 
> Believe me I tried - see above bug report
> 
> > 
> > When @Bill chose to install Mageia 5 RC grub2 on /dev/sda5 he couldn't boot
> > his first distro. Ok, we don't know exactly why, but we know that doing the
> > same with Fedora and Manjaro (installing the grub on root partition) doesn't
> > result in the error produced by Mageia 5 RC installer. 
> > 
> > I hope it's clear now. 
> > 
> > Thanks!
> 
> I'm guessing that this is a duplicate of
> https://bugs.mageia.org/show_bug.cgi?id=15583 then?

Yes, it seems to me that we have a duplicated bug, but @Bill should say this.

So, for the developers this is not a serious issue and it can be corrected on the next release... I disagree, but I'm not a developer!
Comment 36 Barry Jackson 2015-06-01 19:02:24 CEST
(In reply to Geraldo  Witeze Junior from comment #35)

> So, for the developers this is not a serious issue and it can be corrected
> on the next release... I disagree, but I'm not a developer!

It is a serious issue and I share your frustration, however it was not possible in the time available to provide a fix for the Mageia 5 installer.
Comment 37 Barry Jackson 2015-06-01 19:04:05 CEST
Duplicate of 15583

*** This bug has been marked as a duplicate of bug 15583 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE

Comment 38 Geraldo Witeze Junior 2015-06-01 19:09:12 CEST
(In reply to Barry Jackson from comment #36)
> (In reply to Geraldo  Witeze Junior from comment #35)
> 
> > So, for the developers this is not a serious issue and it can be corrected
> > on the next release... I disagree, but I'm not a developer!
> 
> It is a serious issue and I share your frustration, however it was not
> possible in the time available to provide a fix for the Mageia 5 installer.

:^( 

Well, at least I learned how the bug reports works :)

Thank you!

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