You are right, (also for me) the installer creates a GPT (GUID partition table), a bios_grub parttion for BIOS mode and an EFI system partition for UEFI mode by default.
If I understand correctly, only one of these partitions is used when booting, so it should not be necessary to have the EFI system partition, when you boot in BIOS mode. But I have not tried to create partitions manually and I have not checked if we must create both of them when creating partitions manually with the ‘Something else’ option in the installer.
I guess that it is still possible to install Ubuntu and the Ubuntu flavours in an MSDOS partition table, and then the grub ‘extras’ will be in the unallocated space behind the MBR and partition table in the first mibibyte, so there is no [need for a] bios_grub partition. If you wish, you can work through a few test cases with manual partitioning, for example:
Wow! I am impressed. This looks really good. Thank you very much for backporting the Mojave theme to 20.04. As a longtime Mac user I got so used to the look of OS X / macOS that I just couldn’t resist. I had to try out the new theme immediately. My first impression is extremely positive. The theme and the icons are very well done and the font Roboto is a real highlight. However, as I find it difficult to get used to the preferred use of dark themes (but maybe I’m just getting old), I changed the widgets to Mojave-light-solid and the icons to McMojave-circle. There will certainly be some bugs in the Mojave theme, but for now I have to say that this theme suits my Ubuntu Budgie very well.
it seems that is mandatory, I fear. Here my tests results
bios mode, msdos pt, “use whole disk” option leads to a working vm with grub and efi partitions
bios mode, msdos pt, “Something else” option, grub and efi partitions kept from previous #1) installation leads to a working vm with (grub and efi partitions and) a 30 Gb / and a 50 Gb /home
bios mode, msdos pt, “Something else” option (30 and 50 Gb / and /home partitions as above), no grub or efi partitions leads to a warning after partitioning (see screenshot #1) and a fatal error as soon as it comes to grub installation (screenshot #2).
I’m imagining that, efi or bios, it pretends an efi partition anyway … really a strange behaviour!
EDIT
I’ve also tried to install as in test #3) above but adding, during installation, first a bios_boot and a efi partition before creating / and /home (see screenshot below)
Just upgraded 20.04 minimal via sed command and other than having to manually install an Nvidia 390 module for kernel 5.8.0.16 all went well. I had switched to LTS after moving this summer and am ready for testing again.
I did file a bug report #1893489. Interesting, I installed GDM3 and then changed from LightDM to it. It would boot fine with the 5.8 kernel. I did not use wayland
I don’t think this is a real issue, but I figure I’ll mention it anyway. I get this on 20.10 when compiling schemas, but not on 20.04:
No such key “show-nm-trayicon” in schema “com.solus-project.tray” as specified in override file “/usr/share/glib-2.0/schemas/10_budgie-network-manager-applet.gschema.override”; ignoring override for this key.
Clean install, but maybe something I did… The only schema i compile on it is the one for my clock, I purposely haven’t made any other changes on it or compiled anything else to keep it fairly clean for testing…
But it doesn’t happen on my 20.10 VM, so all signs point to me I guess. I’ll try a fresh install later and see if it happens still.
Getting repeated installer crashes with a message regarding grub failing to install. The installation completed and runs perfectly. I have uploaded the crash report. At first I thought the installation failed and tried again, but the OS was already installed. ???
