Ubuntu 22.10 beta freeze at boot

[Mlocik97]

Hello, I installed Ubuntu 22.10 beta on VM (QEMU/KVM with secboot enabled). When booting, it freeze at boot at logo "TianoCore" in middle and "Ubuntu" at bottom, and nothing happens. Tried to use alt + ctrl + F1, but it doesn't work either. So I booted ISO again and checked logs.

logs: https://gist.githubusercontent.com/Mlocik97/f8639d5c2d8bf7d9e08089b47827c639/raw/3b210bbbe76fab1482d4e2e2e3a9dde19458175d/syslog

E: copying answer with reproduction steps (so it's visible):

```
Steps to reproduce:
-Setup a VM in VirtualBox or QEMU/KVM

-Install Ubuntu and check "install third party software..." and reboot
OR
-Install Ubuntu without checking "install third party software..." and then post-install, installing ubuntu-restricted-addons and reboot.
```

source of comment: https://bugs.launchpad.net/ubuntu/+source/ubuntu-restricted-addons/+bug/1991577/comments/7

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

[Launchpad Janitor (janitor)]

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

[Matěj Valášek (valmatej)]

same situation in virtualbox 6.1.38 i discovered if i am pressing ctrl c during boot, it is not freezing, but the right seaquence of pressing ctrl c is not discovered yet.
there is my boot log prevboot.txt file
https://gist.github.com/valmatej/febfef381ff642ff55376dd2c1ae17ca

[emptythevoid (emptythevoid)]

This seems to happen if both "Download updates while installing Ubuntu" and "Install third-party software for graphics..." are checked when doing "Install Ubuntu" or "Try Ubuntu." Another symptom of this issue (only when doing "Install Ubuntu") is when clicking the button at the end of installation to Restart, instead of seeing the logo with the instructions to press Enter, it goes black with an unblinking cursor at the top-left. Pressing Enter will reboot the machine at which point it will hang. The VM will show CPU activity for about a minute or so after the hang occurs, but then CPU activity settles and the hang persists.
Seems the hang is related to enabling "Install third-party software" during install.
Tested using QEMU/KVM.

[emptythevoid (emptythevoid)]

This issue seems to be specific to https://packages.ubuntu.com/jammy/ubuntu-restricted-addons. Skipping the "third party software" checkbox, completing the install, confirming it boots, and *then* installing this package will cause the same hang after a reboot.

[Mlocik97 (mlocik97)]

I tested installing without 3rd party sw, and works for me too. So yes, it seems like that package is causing this. Thank You for identifying problematic package.

[emptythevoid (emptythevoid)]

Steps to reproduce:
-Setup a VM in VirtualBox or QEMU/KVM

-Install Ubuntu and check "install third party software..." and reboot
OR
-Install Ubuntu without checking "install third party software..." and then post-install, installing ubuntu-restricted-addons and reboot.

[emptythevoid (emptythevoid)]

For what it's worth, so far this seems specific to vanilla Ubuntu. I was *not* able to reproduce this behavior on Kubuntu, Lubuntu, Xubuntu, or Ubuntu-Mate.

[emptythevoid (emptythevoid)]

I am able to reproduce this bug by specifically installing the gstreamer1.0-vaapi package from ubuntu-restricted-addons. I also tried individually installing all the dependencies of the gstreamer1.0-vaapi package and none of them caused a problem. It seems that specifically the gstreamer1.0-vaapi package is the one causing this problem.

Edit: this would be gstreamer1.0-vaapi 1.20.3-1

[emptythevoid (emptythevoid)]

I tried installing the gstreamer version from Jammy using dpkg and, after resolving dependencies, it seemed to have the same behavior (my methodology might be poor)

[Matěj Valášek (valmatej)]

I found the exactly same bug reporting this exactly the same issue.
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1988488
I think we can assign this issue as duplicated.