** Description changed: - Ubiquity + [Workaround] + + If you install while completely offline (do not connect WiFi, do not + plug in network cable) then the bug doesn't happen. You can then connect + in the installed system just fine. [Impact] * Certain SKUs of laptops; when networking is enabled; complete the installation successfully, without installing any kernel on the system rendering it unbootable. [Test Case] * Start install on a relevant SKU * Enable networking on * Ensure that after the installation kernel packages are installed in /target * Reboot to observe that installed [Where problems could occur] * Hopefully we will not remove kernels again.... especially the one we want to boot. [Other Info] * Original bug report I was installing ubuntu on my fresh new notebook and found that kernel packages wasn't installed. As workaround to run the system I had to chroot into /target to complete installation. I have one disk and it was partitioned as GPT. Initialy I thought it was a problem with boot loader but I had installed debian without issue(except it not provide proper firmware). Then I tried to boot into ubuntu from debian's grub and found that there are no kernels. It took me 2 days((( - === oem-qemu-meta * To ensure this doesn't happen again, we must update the test oem-qemu- meta package to match the behaviour of the other similar packages in the oem archive.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915114 Title: Ubiquity: No vmlinuz* after install. 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-qemu-meta/+bug/1915114/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
