Ubuntu 23.04 Installer Fails Randomly

[Luis Alvarado]

MOBO: Asus Maximus Z790 Hero
VIDEO: Zotac Nvidia RTX 4090 AMP Extreme AIRO
CPU: Intel i9 13900k
RAM: g.skill 128GB Trident Z5 DDR5 6000Mhz
SSD: WD SN850x 2TB

So I made a video at https://youtu.be/Rk6noG4alOA

Because it is actually random and has multiple issues everywhere. The video shows all the issue so far, but also shows Firefox opening for the first time along with the Dark Theme working again (Although it crashed when changing it using Subiquity).

It would help to know how I would run apport against subiquity to show more about the errors since when I tried it did not actually catch the error.

[Luis Alvarado (luisalvarado)]

I set the affected package as subiquity, not mysql-8.0, do not know why it shows mysql.

[Olivier Gayot (ogayot)]

Thank you for your bug report.

I'll try to list the elements you pointed out to:

1. Slow start of the install (sometimes it's fast, sometimes not)
2. UX: In manual partitioning, double clicking on a partition does not open a dialog to modify/change it
3. UX: In manual partitioning, double clicking on Free space does not open a dialog to add a new partition.
4. In manual partitioning, clearing all partitions from a device (e.g., nvme1n1) and adding a new partition in the free space inserts seems to re-add one of the original partitions: https://pastebin.ubuntu.com/p/rsJzN4ZxXT/
5. Crash report opened when reaching the identity screen (a tarball of /var/log/install + /var/crash would be very helpful to diagnose!)
6. After the crash, clicking on Install Ubuntu 23.04 icon on the desktop does not reopen the installer, but clicking on the icon in the dock does
7. UX: On the network screen, selecting a Wi-Fi network and connecting does not automatically move on to next screen. The move forward button still says "Connect"
8. After connecting to a Wi-Fi, clicking the "Connect" button prompts for the Wi-Fi password again (although it's already connected) but the install seems to continue in the background
9. Install failed again shortly after, the logs show corrupted package cache. Here again, a tarball of the logs would be needed.

[Luis Alvarado (luisalvarado)]

Thank you Oliver, here are the reports thanks to the point 5 that you mentioned:

[Luis Alvarado (luisalvarado)]

Okay, after about 20+ Tests, I was able to remove all issues by setting the ibt=off parameter on grub before starting the ubuntu installation. I then removed ibt and the freezing and failures started. I added ibt=off again and I was literally able, from start to finish, end the installation process without ANY issues. I changed themes, clicks in different places in the installed, formatted and reformatted the partitions, selected 3rd party apps options, etc.. It never crashed, but by simply removing ibt=off I had a 50% chance for the whole thing to either crash or freezes completely where I need to force reboot.

I also was able to noticed that when rebooting (In the scenario that I select try ubuntu without installing and then proceed on rebooting) the reboot process would freeze, but if I set ibt=off it would reboot without issues.

Lastly, without ibt=off in a random way, the first line when booting would say that the init is corrupt. With ibt=off it would boot properly.

[Luis Alvarado (luisalvarado)]

Just updating. This is fixed. On Beta with Update April 10 there is no issue and here is the list of other things fixed:

1. Rebooting after installing from USB no longer freezes before rebooting.
2. Nvidia drivers are now installed properly which includes nvidia settings working correctly.
3. Changing to Xorg and disabling Wayland no longer freezes the system on boot.
4. Changing resolution no longer causes a black screen in a random way I was not able to assess.
5. Waiting for the suspend to kick in no longer freezes computer if you try to move the mouse or keyboard.
6. I installed 5 times already today without putting any kernel settings and it worked properly.

[Dan Bungert (dbungert)]

Luis, I greatly appreciate the update. It sounds like a fix in general appeared in the archive and this wasn't ubuntu specific.

I'm going to mark these as "Invalid", the state used when we're taking no action. If you see continued problems feel free to update here or file a new report. Thanks!

[Luis Alvarado (luisalvarado)]

Awesome, thank you Dan.

[Mahboub Hosseinzadeh (alishserver)]

I also have this problem. The last file I downloaded from the official Ubuntu site was today, but it didn't work for me. I'm waiting for this bug to be fixed.

Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Early/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Early/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Reporting/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Reporting/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Error/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Error/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Userdata/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Userdata/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Package/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Package/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Debconf/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Debconf/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Kernel/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Kernel/apply_autoinstall_config