[apport] ubiquity crashed with OSError in _execvpe()

This looks like either a bad CD burn or a dying CD-ROM drive. Are you able to test again with a different CD, preferably Ubuntu 7.10?

Thanks!

Hi Evan,

    First of all, I'm a newbie, so don't expect much in the area of
troubleshooting or knowing what to look for.

    Thanks for the message and suggestions. This happened months ago,
and I've forgotten the details -- sorry. As best I can recall, I
started the installation, got the error message, didn't really know what
to do but filed an incident report anyway, then either continued on with
the installation or re-booted, started the install again, had no further
"incidents" , and was successful in installing Ubuntu. I've installed
versions 7.04 and 7.10 in the past, so can't tell you which one caused
the "report" to be filed. I wish I could remember the details better,
because I'd really like to help chase down "bugs". I've installed other
distros and not experienced this problem, by the way.

    Maybe you could help me with another "bug" that I've experienced
with all versions of Ubuntu since Breezy? I'll briefly describe it:
the sound is messed up and system responses are delayed by maybe 30
seconds. The "fix" is to add "irqpoll" to the kernel boot line in
/boot/grub/menu.lst . If you're willing to work with me on this, let me
know and I'll supply more details.

                Jerry

Evan Dandrea wrote:
> This looks like either a bad CD burn or a dying CD-ROM drive. Are you
> able to test again with a different CD, preferably Ubuntu 7.10?
>
> Thanks!
>
> ** Changed in: ubiquity (Ubuntu)
> Status: Confirmed => Incomplete
>
>

That's quite ok, I am fairly certain that this bug was caused by the problem I described above, so I'm closing it. As for your other issue, please open a new bug report against the linux-source-2.6.22 package (if you're using Gutsy) and attach the following to it:

uname -a > uname-a.log
cat /proc/version_signature > version.log
dmesg > dmesg.log
sudo lspci -vvnn > lspci-vvnn.log
cat /proc/interrupts > interrupts.log

Don't forget to give the bug report a detailed description of the problem. Thanks, and good luck.