Ubuntu Jammy Desktop fails to boot after install

Bug #1960226 reported by Leó Kolbeinsson
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

Ubuntu Jammy Desktop fails to boot after install

Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07

This also affects Ubuntu Jammy Canary desktop - tested daily ISO 2022-02-07

After installing the OS and selecting reboot the system reboot fails -

The vendors logo appears with the Ubuntu logo and fails to boot - I have tried this with 2 barebone machines and 1 in VirtualBox - will attach syslogs and images in a separate comment.

Revision history for this message
Leó Kolbeinsson (leok) wrote :

Link to my results Ubuntu Jammy Desktop daily ISO - 2022-02-07

http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244047/testcases/1300/results

Attached is syslog for the Dell latitude 7280 - I have all the other install logs available if needed.

Revision history for this message
Leó Kolbeinsson (leok) wrote :

And here screenshot of the systems boot failure - only the logo screens and all hangs.

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

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

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

tags: added: iso-testing
Revision history for this message
Julian Andres Klode (juliank) wrote :

You have already left grub at this point and the kernel also started.

Reassigning to systemd in the meantime to debug this further as a userspace boot issue. This might need further reassing.

You'll have to boot this verbosely, it's no use with a splash screen enabled.

affects: grub2 (Ubuntu) → systemd (Ubuntu)
Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Leó Kolbeinsson (leok) wrote :

@juliank

I will retest this again after release next daily ISO on other machines as well.

Revision history for this message
Leó Kolbeinsson (leok) wrote :

This also affects Ubuntu Jammy Canary desktop - tested daily ISO 2022-02-07

description: updated
tags: added: jammy
Revision history for this message
Leó Kolbeinsson (leok) wrote :

Retested Ubuntu Jammy daily ISO 2022-02-08 - again fails to boot to desktop after install.

http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244085/testcases/1300/results

Revision history for this message
Chris Guiver (guiverc) wrote (last edit ):

this comment is likely invalid... see "--- update"

I zsync'd the daily & completed 3 installs but did NOT experience this issue

uEFI - sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
BIOS - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

the sony 'thingy' had two installs to it;
- one using normal uEFI, and
- the other using Secure-uEFI
reports can be found at link provided in Leó's comment #7

-- update

the sony thingy doesn’t have the expected date on /etc/apt/sources.list

-rw------- 1 guiverc guiverc 3.1G Feb 2 09:38 jammy-desktop-amd64.iso
-rw-rw-r-- 1 guiverc guiverc 56K Feb 2 18:56 jammy-desktop-amd64.manifest
-rw-rw-r-- 1 guiverc guiverc 6.2M Feb 2 19:40 jammy-desktop-amd64.iso.zsync

that date & what’s on the sources doesn’t match Download links for Ubuntu Desktop amd64 | Ubuntu QA

SO I'll HAVE TO DISQUALIFY MY COMMENT.

My ISO was from http://cdimage.ubuntu.com/ubuntu/daily-live/current/jammy-desktop-amd64.iso

where https://cdimage.ubuntu.com/ubuntu/daily-live/current/ shows the manifest I download & a zsync file matching Feb-2 ... so my ISO is OLD !

is something wrong here? is this related? or maybe I've just got to check my zsync script.. is the issue just web site/zsync related? no time to currently look

Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

2022-02-02 WORKS
2022-02-03 WORKS
2022-02-04 ?
2022-02-05 FAILS
2022-02-06 FAILS
2022-02-07 FAILS
2022-02-08 FAILS
2022-02-09 FAILS

Sorry I don't have a copy of 2022-02-04 to test.

Changed in systemd (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

Here's the diff between working and not working.

Edit: Sorry, ignore this comment. It's the package list of the live session whereas we want the installation itself.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Although this is one of the changes:

https://launchpad.net/ubuntu/+source/ubuntu-meta/1.475

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Given the bug doesn't occur for upgrades, maybe this change is relevant:

https://launchpad.net/ubuntu/+source/ubiquity/22.04.6

(the working image has 22.04.4)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Seems the problem is not ubiquity. Downgrading to 22.04.4 before installing made no improvement.

no longer affects: ubiquity (Ubuntu)
Revision history for this message
Leó Kolbeinsson (leok) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I was thinking gdm3 needed some investigation but this update was published an hour ago:

  https://launchpad.net/ubuntu/+source/gdm3/41.3-1ubuntu2

Fingers crossed.

Changed in gdm3 (Ubuntu):
status: New → Fix Committed
no longer affects: systemd (Ubuntu)
no longer affects: ubuntu-meta (Ubuntu)
Changed in gdm3 (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Verified fixed in 2022-02-10

gdm3 = 41.3-1ubuntu2

Changed in gdm3 (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Leó Kolbeinsson (leok) wrote :

I can confirm that the fix works - bug no longer present.

Tested Ubuntu Jammy daily ISO 2022-02-10

http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244168/testcases/1300/results

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.