VM fails to reach user session after dist upgrade from focal to jammy

Bug #1953470 reported by Olivier Tilloy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I just verified that bug #1951096 is fixed by dist-upgrading a fully up-to-date focal amd64 VM to jammy, but after rebooting I'm getting a completely blank (aubergine) screen, and I cannot even switch to a VT using the usual key combinations (Host+F<n> in VirtualBox).

Fortunately that VM had an ssh server running so I was able to ssh into it and get the system journal, which I'm attaching here.
I'm also attaching the dist-upgrade log in case it's useful, and I can provide more info if needed (I'll keep a snapshot of the VM in that broken state).

Revision history for this message
Olivier Tilloy (osomon) wrote :
Revision history for this message
Olivier Tilloy (osomon) wrote :
Olivier Tilloy (osomon)
tags: added: rls-jj-incoming
summary: - VM fails to reach user session after dist upgrade from focal to jammy,
+ VM fails to reach user session after dist upgrade from focal to jammy
Revision history for this message
Brian Murray (brian-murray) wrote :

I upgraded a focal vm to jammy today and was unable to recreate this issue. I see the desktop when choosing either a wayland session or an xorg session.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
Revision history for this message
Olivier Tilloy (osomon) wrote :

I can still reproduce in that same focal VM, fully up-to-date, when dist-upgrading it to jammy.
I wonder if this has to do with the fact that it's configured for auto-login.
I'll have to test again in a brand new focal VM.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Just tested again in a brand new and fully up-to-date focal VM that I installed from the 20.04.3 desktop iso, then dist-upgraded to jammy, and I am not seeing the problem.

If it's reproducible only in that specific VM that has auto-login enabled, and probably other cruft, I think the bug can be safely closed.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Invalid
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.