Ubuntu

22.04 LTS Desktop Daily Builds hang on the Plymouth Screen with VirtualBox on Windows

Bug #1969652 reported by Oliver Smith
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
New
Undecided
Unassigned
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

In Virtual Box (running on Windows 11) the Plymouth screen hangs (spinner disappears, screen frozen) when running the 22.04 LTS daily build (this occurs across multiple daily builds) for the first time (booting from the ISO).

On occasion it is possible to progress and complete an install of 22.04, however upon reboot the same issue occurs.

Same issues is currently present on the default 21.10 image but not on the default 20.04 image.

Issue has been replicated by Ken VanDine on Windows 10 with and without Hypervisor enabled- but the issue mostly arises during a reboot after install in that instance.

Tags: bot-comment
Revision history for this message
Ken VanDine (ken-vandine) wrote :

I've reproduced this with the current daily jammy iso as well as with debian 11. It hangs on boot with the Plymouth screen.

Changed in ubuntu:
status: New → Confirmed
summary: - 22.04 LTS Desktop Daily Builds hang on the Plymouth Screen on VirtualBox
+ 22.04 LTS Desktop Daily Builds hang on the Plymouth Screen with
+ VirtualBox on Windows
Revision history for this message
Ken VanDine (ken-vandine) wrote :

I also tested the virtualbox 6.1 on linux and the install works fine. It seems to be isolated to Windows 10/11 hosts, which unfortunately has a much bigger footprint.

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

I wonder where the hang actually happens, at which stage exactly. I wonder if we could get a run without splash and without quiet to see a bit more debugging info, maybe even with debug=efi?

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Also: is the VM hanged, or is there a blinking cursor on top? Can the tty be changed?

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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/1969652/+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.]

tags: added: bot-comment
Revision history for this message
Brian Murray (brian-murray) wrote :

I wonder if this is similar to bug 1969524 and it is an issue with trying to use wayland.

Revision history for this message
Ken VanDine (ken-vandine) wrote :

I do think this is wayland related, after disabling wayland in GDM it does appear to work. I disabled it by editing /etc/gdm3/custom.conf. With wayland disabled, it takes a really long time to show gdm though.

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

Other bug subscribers

Remote bug watches

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