I'm afraid that there is nothing we can do about this without the
requested log files. If you (the original reporter) can reproduce this
bug with a current release and can get us the log files, feel free to
reopen this bug. (Anyone else reading this who believes they have a
similar problem should open a new bug instead.)
In any case, exit code 135 translates to "bus error" (i.e. a bad memory
access); the only real way that can happen in this particular context is
if there's been a problem reading from the CD. This is generally due to
a faulty CD/DVD disk or drive, rather than being an installer bug as
such. It may help to clean the CD/DVD, to burn the CD/DVD at a lower
speed, or to clean the CD/DVD drive lens (cleaning kits are often
available from electronics suppliers). Sometimes, this may also be due
to a faulty hard disk, and in that case replacing it or moving the
system to a cooler environment might help. We can't tell which without
log files.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
Installer Crashed at 78%
https://bugs.launchpad.net/bugs/163719
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
