Comment 5 for bug 2000066

Thank you for your insights, David. That is very helpful!

There are two processes involved in a Subiquity installation:
1. the server process which stores the data and actually performs the install
2. the client process which shows the UI and communicates with the server.

The crash that happens when editing the encrypted VG is a crash on the client side. When that happens, a new client process is started (and it starts over from the first screen) but the server does not automatically discard the data entered so far. I believe this inconsistency is what caused the presence of an encrypted LVM even though you chose not to on your third attempt.

I just submitted a patch to fix the crash when editing the encrypted VG: https://github.com/canonical/subiquity/pull/1532

As for the first crash that you encountered, sadly this is a bit of a mystery for me. If there is any log that you can share from this run (possibly in a different bug report), we will have a look.

Best regards,
Olivier