vmlinuz file not found error after selecting a different iso boot kernel

Bug #1773048 reported by Cubic PPA
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cubic
Fix Released
Medium
Cubic PPA
Classic-development
Fix Released
Medium
Cubic PPA
Release-2018-07-34
Fix Released
Undecided
Unassigned

Bug Description

When booting a custom Live ISO that was created by selecting a different boot kernel in Cubic, the Live ISO will not boot. The error "casper/vmlinuz: file not found" appears on the screen when booting the customized Live ISO.

Revision history for this message
Cubic PPA (cubic-wizard) wrote :
Cubic PPA (cubic-wizard)
description: updated
Changed in cubic:
assignee: nobody → Cubic PPA (cubic-wizard)
importance: Undecided → Medium
Revision history for this message
Thorsten Wagner (totto) wrote :

I can reproduce the error, but also with the original kernel of bionic beaver (Ubuntu 18.04) I can not get a working iso. Definetely, the outcome in both cases is different, meaning that the boot process fails at different stages (initial boot for custom kernel, after "try ubuntu" for original kernel).

Revision history for this message
Cubic PPA (cubic-wizard) wrote :

A side effect of Cubic's capability of selecting an ISO boot kernel resulted in an unbootable ISO, even when the default original ISO kernel is selected.

For release 2018.06-29, temporarily disabled Cubic's ability to change the ISO boot kernel. (Only the default kernel will be listed, even though other kernels may be available).

Thus, the ISO's original kernel will be used by Cubic, and this should eliminate the boot issues.

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

Other bug subscribers

Remote bug watches

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