There was some discussion regarding this particular bug in #ubuntu- release on 20190620 - https://irclogs.ubuntu.com/2019/06/20/%23ubuntu- release.html. I will not summarize the conversation here but only capture what I understand the bug in initramfs-tools to be.
update-initramfs no longer uses what is in /var/lib/initramfs-tools as a source of knowledge about kernel versions so using "-k all" will not bring a deleted initrd. This behavior does not match the documentation and is a regression. Some choice quotes follow: "[20:52] <infinity> That appears to completely ignore STATEDIR now. [20:59] <infinity> Anyhow, the behaviour change above is that it switched from checking STATEDIR to stating the initrd. [20:59] <infinity> So, instead of "statedir knows what we've done in the past", we have "in you have no initrd, you can't have a new one either". [20:59] <infinity> s/in you/if you/ [21:02] <infinity> https://salsa.debian.org/kernel-team/initramfs-tools/commit/f39625afd6ba6c1aa2027286dc3ef1c933da14e0 [21:03] <infinity> vorlon: That would be the offending commit. I think the obvious way to get both old and new behaviour combined would just be to add the statedir bit to the list (and sort -u the mess)." ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Triaged ** Bug watch added: Debian Bug tracker #926401 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926401 ** Also affects: initramfs-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926401 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in calamares-settings-ubuntu package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Triaged Status in initramfs-tools package in Debian: Unknown Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
