This issue has been fixed on NEW installs, but on re-installs or ‘install using existing partition’ I’m still experiencing this error on first login after re-install. I wonder if something survives in $HOME given it’s untouched in this install case…
Further we may also have issues with release-upgrades from 23.04?? and test for it. (Changelog)
Listed here as I’m unsure if worthy of noting on primary list, but also don’t want to forget it. Any comments on this thread are welcome, the first post contains the list that matters, and readers can use HOME to quickly view that list
I am not experiencing #1922342 here. I went through a legacy boot cycle a couple of times to check that.
I’m not sure if there’s a difference. I can boot the device UEFI and ‘legacy’ via the system settings. But, is ‘legacy’ really BIOS mode? That’s the fairly new MSI laptop that I purchased just for testing. I can’t be confident of the pre-boot computation, but in legacy mode the 20231010 daily .iso boots in about the same time it always does.
I rarely boot ISOs on a motion computing device I have because it means 9+ minutes of seeing nothing but black screen during the boot (boring!)
The issue is a firmware bug that exists in a small variety of devices that makes installing a new OS take an extra 10 minutes, so hardly a big deal, but sure is noticeable if using the device to test booting ISOs. The ISO can be reformatted to make it boot 8+ minutes faster, alas the ISO then can’t be used to boot on other machines, so I’d not recommend it.
I also hit it on another box that also has the firmware bug (this one a lenovo) but it’s a non-compliance issue within the firmware where the OEM/maker didn’t care as the OS the device was sold with was pre-installed.
We’ve documented the issue here
and that’s sufficient in my view. It impacts less than 1 in 5000 boxes (specific firmware code get triggered). Maybe the 22.04 in that link needs to be made less jammy specific.