The bug was only fixed in our Calamares configuration and still needs to
be fixed in initramfs-tools.
Adjusting bug statuses appropriately and adding the release tag. I'll
ping vorlon and xnox on IRC to get their take.
** Also affects: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided
The fix is now released. Spinning up a new ISO as we speak.
calamares-settings-ubuntu (1:19.10.2) eoan; urgency=medium
* Fix initramfs job failing. Thanks to TJ for the fix! (LP: #1829805)
* Move before_bootloader_mkdirs process before initramfs.
* Workaround bug in
Just to add my $.02 . . . I also had this problem with perhaps 6/12
daily and then I zsyncd what I think is the 6/15 daily . . . finding the
same "kernel panic" report as Dan found. A couple days later I
downloaded a fresh 19.04 iso and ran the install . . . and that went
well.
Glad to hear that
I have tested this patch in virtualbox and it works for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829805
Title:
Lubuntu Eoan Daily Image fails to boot after install on KVM
We got a potential fix thanks to TJ that seems to be working wonderfully from
what I can ascertain:
https://phab.lubuntu.me/D15
Download the raw diff, cd /etc/calamares, sudo patch --strip 2 <
/path/to/diff, and install like normal. Done!
--
You received this bug notification because you are a
We have a second bug that causes the call by update-
initramfs::get_sorted_versions() to report nothing when calling
(/usr/bin/) "linux-versions list".
This because the target root file-system is copied from the
filesystem.squashfs on the ISO which does NOT contain a
/boot/vmlinuz-$(uname -r).
I should have made clear, this 'second bug' is the only bug.
initrmafs-tools is in the clear - it wasn't finding a kernel image
because there wasn't one when update-initramfs was executed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Or is it? Actually I not, because the test in update-
initramfs::get_sorted_versions() expects an existing
initrd.img-$version:
get_sorted_versions()
{
version_list="$(
linux-version list |
while read -r version; do
test -e
After many hours diving down rabbit holes it turns out this is due to a
major change in the behaviour of update-initramfs introduced by Debian
in July 2018 which made its way into the Ubuntu archive end of april
2019.
01:02 Right! initramfs-tools had a MAJOR import from Debian with
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
The problem seems to be in the calamares configuration. The initramfs
task is being called before the target's live-* packages have been
removed. This is specifically warned about in the calamares initramfs
module but we see the timestamps of the initramfs task are before the
live-* packages are
The problem here is the installer failed to build/install initrd.img.
After installing into a LVM LV via libvirt and seeing the error I
mounted the disk image contained in the LV and explored:
$ sudo losetup -f --show -P /dev/VG02/lubuntu1910
/dev/loop5
$ sudo mount /dev/loop5p1 /mnt/target
$
It appears from the screenshot the panic is occurring because the
initramfs /init script is failing to find and mount the real root file-
system.
You can drop to a busybox shell in the initramfs by adding a kernel-
command line option manually in the GRUB boot menu.
Tap Esc key to get to the
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Same problem with me: Version "2019-06-05 16:52" is fine in live mode,
but kernel-panics after installation and attempt to boot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829805
I tested today's (5/23/2019) ISO image in virtualbox and while it still
fails, I was able to note that I could mount the installed OS file
system from the live environment.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have tested this using the daily iso image (5/21/2019) on a bare metal
Acer laptop (BIOS) and Virtual Box using both BIOS and EFI. All tests
yield the same kernel panic result.
I have also tested the daily iso (5/20/2019) for Kubuntu and Xubuntu,
both of them worked properly on the same VM
I am unable to get the system to boot to run apport-collect.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829805
The screenshot has a kernel error, reassigning
** Package changed: grub2 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829805
Title:
Lubuntu Eoan Daily
19 matches
Mail list logo