Thanks, we'll take a look.

It sounds like the install completed successfully otherwise? If so there should be logs at /var/log/installer and I'd like very much to see them. We'll also try to produce this locally.

If you want to post the logs without having them visible to the whole world you could file a new bug at https://bugs.launchpad.net/subiquity/+filebug and use this option to mark it private.

Here's the installer log folder. I went through and deleted my user name and password. The install was successful otherwise. Grub was installed, but it doesn't list the Windows partition because the EFi was erased. Sorry, I should have also mentioned that I use the reFind boot loader.

Let me know if you need anything else.

installer_Issue_1772.zip

I'm sorry that the EFI partition was wiped, and I appreciate the logs. I think we have enough info to proceed with a fix. I also appreciate the note about reFind boot loader, but suspect it isn't a factor in this case.

@mcoyle1960 - I notice during logfile analysis that you had used Ventoy. There was a known issue with that, LP: #2012722, which caused us to not gather complete information about the filesystems.

If you were to try again with the 20230404 or newer ISO, that has the Ventoy fix, or to skip using Ventoy, I expect you would not see the problem. When things are working correctly, in the manual partitioning screen, it will show the filesystem types of the partitions. When things are not working correctly, that fs type column is empty.

To be clear, I'm not blaming Ventoy here, it is that Subiquity handled it poorly.

I have an additional fix as well, in the form of canonical/subiquity#1636 which increases the cases in which we gather the filesystem type info. While I believe that that fix will be sufficient, I'm considering additional fixes as well.

@dbungert, thank you for the update. When I experienced this bug, I though of two things: I'm making some mistake OR this is a big deal. I'm very relieved to see you jump on it so quickly. I'd hate to see it somehow tarnish the release of 23.04 and Subiquity.

I did a final round of testing today with the 20230407 build ISO and believe that this is resolved. Thanks again for testing and the bug report.