casper: /scripts/casper-premount/20isoscan: line 59: try_mount: not found

Bug #1841455 reported by Benoit THIBAUD
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu CD Images
New
Undecided
Unassigned

Bug Description

I tried the daily build of xubuntu eoan 2019 08 26.

I can't launch it. Tried with this 2 grub's menus:
menuentry ".. Xubuntu Daily" {
 iso_path="/isos/eoan-desktop-amd64.iso"
 export iso_path
 search --set=root --file $iso_path
 loopback loop $iso_path
 root=(loop)
 configfile /boot/grub/grub.cfg
 loopback --delete loop
}
menuentry ".. Xubuntu .... test daily" {
 iso_path="/isos/eoan-desktop-amd64.iso"
 loopback loop $iso_path
 linux (loop)/casper/vmlinuz locale=fr_FR bootkbd=fr console-setup/layoutcode=fr iso-scan/filename=$iso_path boot=casper file=/cdrom/preseed/xubuntu.seed noprompt quiet splash --
 initrd (loop)/casper/initrd
}
The error about the casper script is from the second menu. But in both cases it can't mount the iso file.

Revision history for this message
John Little (john-b-little) wrote :

I was trying the Kubuntu eoan daily build. I had a look in the squashfs. In the initramfs-tools/scripts/casper-premount/20iso_scan script, it invokes the find_path function, which is defined in scripts/lupin-helpers. It's line 59 of that script that has the try_mount invocation. In my disco iso the try_mount function is defined in scripts/casper-helpers, but the eoan version does not.

Chris Guiver (guiverc)
tags: added: eoan iso-testing
Revision history for this message
John Little (john-b-little) wrote :

Just today downloaded the Kubuntu eoan-desktop-amd64.iso for 2019-09-26, and did an iso boot into it with no problem. So it seems fixed for me.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

casper (1.418) eoan; urgency=medium

  * scripts/casper-helpers: Reintroduce try_mount() function, which was in
    use by (at least) VMWare in a custom installer scenario (LP: #1845535)

 -- Adam Conrad <email address hidden> Thu, 26 Sep 2019 11:00:40 -0600

Revision history for this message
Benoit THIBAUD (frombenny) wrote :

Status should be -> fix released (like in the duplicate bug #1845535)
I tested it, now it's working.

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.