Package: iso-scan
Version: 1.53
Severity: important
Tags: d-i
Dear Debian Install System Team,
I found a bug using iso-scan in the installer image downloaded from
dated 2 Aug 2014.
The bug is only triggered under the following conditions:
1) debconf priority = high or greater
2) More than one iso image in the folder where iso-scan detects an iso.
I marked it important, though, because of the consequences. In my case, I started to see this error in console 2 when trying to ls:
ls: /lib/libc.so.6: version 'GLIBC_2.15' not found (required by ls)
As you can imagine, this meant I couldn't do ANYTHING after this, other than hold the power button down on the computer for 5 seconds. Every menu item fails, including the Abort menu item.
The problem was that I had two iso-scan images on the root of the partition. The first one alphabetically was a CD for wheezy, while the second was the one I wanted ... for jessie. What iso-scan did, under high debconf priority, was just use the first iso, even though it was inappropriate for the jessie installer. I got a warning about no modules, and after that was when the GLIBC error started coming up. It didn't matter what response I selected to the modules error; it was already too late.
If instead debconf is set to medium or low, iso-scan asks which iso you want to use. This should be the behaviour, no matter what the debconf level, if more than one iso image is found. Otherwise we go from asking for a scan to complete failure, just for having two isos in the folder.
Chris