Comment 6 for bug 1914521

Of note..

Last change to calamares is 27-Feb-2020 kc2bez; (http://changelogs.ubuntu.com/changelogs/pool/universe/c/calamares/calamares_3.2.20-0ubuntu1/changelog)

Last release I would have used box to test with SIGNIFICANTLY is 20.04.1 (https://fridge.ubuntu.com/2020/08/06/ubuntu-20-04-1-lts-released/)

thus NO CHANGES WERE MADE to code, yet I had not experienced this before with this COMMON install routine (full disk followed by install alongside).

I've had the opinion that 1864787 would occur on multiple spins of ISO, then stop occurring awhile, before it re-occurred.. (ie. no related code changes, just re-spin of ISO on new daily). When issue occurred (ie. specific daily ISO), it was easy to re-create, on other ISOs (different daily) I couldn't get issue to occur.

The two dailies this occurred on I believe had no meaningful change, http://iso.qa.ubuntu.com/qatracker/reports/bugs/1914521 which I believe was (#ubuntu-flavors)

"<sil2100> We have to fix a rather obscure, but serious (for OEM scenarios) ubuntu-drivers-common bug
<sil2100> Meaning we'll have to eh, respin the desktop isos"

but even for dailies before then (when issue did not occur), I can't see how the lower Ubuntu infrastructure changes could cause it to work flawlessly, then not...

My point is, I'm not convinced this is worth effort, at least with older focal code (3.2.20-0ubuntu1)

If it occurs with hirsute.. then yep as it's later code (two upstream releases later currently).