I’m testing today’s 20200315 image. There is no QA testcase for “alongside.” But, I tried it. It erred with “command: sfdisk --force --append /dev/sda” “Failed to add partition ‘New Partition’ to device ‘/dev/sda’.” (It repeats that failure msg twice on the same line.).
However, when I start the install a 2nd time, the partition was shrunk, and a new partition exists. If I choose “replace partition” it works fine. (So, it doesn’t seem like anything actually failed the first attempt at “alongside.” I just have to do two steps to get through the installation.).
I’ve tried this twice. It failed (but worked with replace partition on the newly-created partition) both times.
This is happening on i5-4200M 2.5Ghz; 4th gen core processor 4600 gfx; Intel 7260 (Lenovo ThinkPad E440 20C5 laptop). It has a Hitachi 500gb Sata3 hdd, 7200rpm. (HTS725050A7E360). The machine is CSM/legacy bios and is installing MBR/bios (not UEFI/GPT).
I can try “install alongside” with a different machine to see if it’s specific to this one.
(I can’t remember if I ever tried “alongside” with Lubuntu. I’m learning that I need to keep a spreadsheet of the machines & desktops I test; what I do differently with each one; what problems I find; etc. I’m keeping notes, but I can’t pivot on that data to see things grouped differently.).