Ubiquity invokes the grub-installer bash script to perform the actual
boot loader install stuff - it reads the the grub-installer/bootdev
debconf value to know where to install the bootloader.
There is some logic in there to find a default boot device which I
suspect is how it's picking the first
I finally got ubiquity running in a debugger and it looks like the
previous code I mentioned is working fine. Ubiquity is correctly setting
the grub-installer/bootdev debconf value. The bug may lie in the grub-
installer program.
--
You received this bug notification because you are a member of
I believe the bug is in this function
https://git.launchpad.net/ubuntu/+source/ubiquity/tree/ubiquity/plugins/ubi-
partman.py?h=applied/ubuntu/impish#n797 (I may have selected the wrong
branch here but the same code is present in the 21.10 live CD).
I reported #1591352 when I was in high school
** Attachment removed: "Debug stuff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1591352/+attachment/4699835/+files/debug%20stuff.zip
** Attachment added: "debug stuff.zip"
I'm reattaching the debug stuff. I didn't realize it logged passwords..
I replaced them with asdfasdf.
** Attachment removed: "Ubiquity debug file, partman, and syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1591352/+attachment/4681249/+files/debug%20stuff.zip
** Attachment
Public bug reported:
I'm installing Ubuntu 16.04 onto an external HDD. My computer also has
an internal Windows 10 HDD.
When at the partitioning stage, it selected for the boot loader to be
installed onto the external HDD.
When Uniquity is installing the system, it mounts Windows 10's ESP and
