Ubuntu Lunar - unable to login after install

[Leó Kolbeinsson]

Testing Ubuntu Lunar daily ISO dated 2022-12-13

The install completes with no errors but after removing media and rebooting the login screen never appears,but the Ubuntu logo and spinning icon are visible and nothing happens even after very long wait (10 minutes).

This was tested on 2 machines:

1. Dell OptiPlex 7040 running in UEFI mode
2.Dell Latitude running in UEFI+secure boot mode

Test results : http://iso.qa.ubuntu.com/qatracker/milestones/441/builds/265902/testcases/1300/results

Attached is screenshot

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1999506

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bernard Stafford (bernard010)]

QA Testing Build 20221213 in Virtualbox.
After install completed and ejected DVD and Restart.
Ubiquity did not start the OS. Stuck on start page with spinner.
Entire disk install.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1999506/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Mike Ferreira (mafoelffen)]

I think it's snap package 'ubuntu-desktop-installer'... On one of mine I tested (KVM Host i9-10900 pass-through vcpu). In the new UI of. At first mine would go to the language chooser, then the 'try/install' panel, but the UI was in a wrong resolution, so the lower parts of the panels were cut-off.

I reported this in Bug: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/1999560

To get around that, I killed Xorg, which then went to GDM3 for installer user, which got me to the desktop, with the resolution fixed. When it started the installer from there, it was the newer UI installer, which I could then see the buttons at the bottom. Finished the install.

that got me to this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1999506

On first boot, the boot hung. Pressing the down arrow got me to the background messaging, where I could see that it started cloud-config and hung on a cloud-init.service start job... until it timed out on fail about 5 minutes later.

It then started a start job on the NetworkManager-dispatcher, which took 10 minutes to fail/timeout.

Where it then started a hold on a boot process cleanup job, which took another (forever). It kept adding time to the counter. I stopped it 30 minutes int the boot process...

[Mike Ferreira (mafoelffen)]

Note that the same ISO was successful install on anohter of my KVM Servers as guest with i-7-2760QM pass-through, but on that it installed as the older UI installer.

[Bernard Stafford (bernard010)]

Build 20221214 Ubiquity crashed between restart of install to startup page.
I was able to open the terminal with ctl+alt+t.
Screenshot as an attachment. Waiting for 14 minutes for start page to start, nothing.
6GB memory and 2core processor. Installed in Virtual box.

[Mike Ferreira (mafoelffen)]

I noticed today, that during the install, if you look at terminal, when it's creating one of the cloud config files (just an observation) it looks like one of the files it is creating has "\n" (escape n) characters inserted into the file. It only happens with one file.

When it hangs in the boot, it is in cloud-init... Coincidence?

[Mike Ferreira (mafoelffen)]

Never mind #9... I mounted the installed image with the ISO. The cloud-int files looked good. There are messages within there, where the "\n" is good.

I chrooted into the installed system, refreshed the instramfs images via: update-initramfs -c -k all

And rebooted the system.. It came up fine on that reboot as the first boot.

That fixed it.

[Leó Kolbeinsson (leok)]

Build Ubuntu Lunar daily 20221216 2 installs with no errors - all good

Test results : http://iso.qa.ubuntu.com/qatracker/milestones/441/builds/266112/testcases/1300/results

[Mike Ferreira (mafoelffen)]

2 more Installs, Lunar Daily 20221216 good. No errors.