I am having an issue with the Kubuntu installer for 23.04 ignoring my choice of bootloader location. I have a dual boot scenario where i have two drives. One drive contains a windows installation, and the other is completely empty and is the place I want to put my Kubuntu Install. I go through the installer, and select manual partition. I create an EFI partition, swap partition, and a root partition for Kubuntu. I then select the correct drive that i want the bootloader to install to. The installation completes just fine, but when I reboot, the bootloader has been installed to my Windows drive rather than the one i specified for Kubuntu on its own drive. I know that the bootloader was installed to the wrong location in 2 ways. First, my motherboard list the devie name for bootable media, and both windows and Kubuntu showed up on the same device(the 2 disks i have are different models). Second, In windows I mount both EFI partitions on the two drives and look at their partitions. I see the BOOT and ubnuntu folder on my windows EFI and not in the Kubuntu EFI which is entirely empty. I have gone through process of wiping and reinstalling 3 times now taking extra care to make sure i have the correct bootloader device selected. It seems like the installer is just ignoring my choice, and putting the EFI onto my Windows partition.
After looking around for awhile, i found a bug report going back to 2014:
Bug #1396379 “installer uses first EFI system partition found ev...” : Bugs : ubiquity package : Ubuntu (launchpad.net)
It has remained unfixed for years and appears to be related to the ubiquity installer.
Is there any way to get around this issue?
There seems to be some chatter that the flutter installer(Ubuntu's new installer) does not have this issue. Will Kubuntu be moving to this installer at a later date?
After looking around for awhile, i found a bug report going back to 2014:
Bug #1396379 “installer uses first EFI system partition found ev...” : Bugs : ubiquity package : Ubuntu (launchpad.net)
It has remained unfixed for years and appears to be related to the ubiquity installer.
Is there any way to get around this issue?
There seems to be some chatter that the flutter installer(Ubuntu's new installer) does not have this issue. Will Kubuntu be moving to this installer at a later date?
Comment