Dear All, especiall UBUNTU Ubiquity team and The Boss (Mr. Mark)
It has been long time since I report this bug.
And so many of us are effected.
Today I have made experiments and have short cl1&cl2 many times again to
help UBUNTU community.
I have reformat my SSD and install Windows 10 in UEFI mo
Public bug reported:
It is similar almost the same.
But I decide to file a separate report of bugs from
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703
Because it destroy existing grub that was not reported there.
And this time I hope the guru will see what informations wer
Sorry I could not find the old edit link to go and edit my post so I
repeat the part that need modifications/
My conclusion is Moderator must now file this as real bugs in 18.04
The bugs lies in the 4 parts.
1. It did not detect that we have BIOS mode installations in place,
like the 16.04.4
@Graham Mitchell (graham-grahammitchell)
I view the same as yours.
More though, there is or are the bugs somewhere in the new 18.04 Ubuntu, Kylyn,
Lubuntu.
I confirmed the problems.
https://askubuntu.com/questions/1028921/the-grub-efi-amd64-signed-
package-failed-to-install-into-target-during-in
Dear Fillippo
Do you mean.1. After we inatalled uefi ubuntu and it destroy Lifebook multi
boot function in Bios.2. Instead of opening the Main Board to shorting CL1/CL2
posts, you can retorethe Option of Multiboot of the bios by just adding an
entry via windows using an uefi entry manager?
If y
