Boot option "safe graphics mode" not in kubuntu maverick install cd

I don't believe this is a grub problem. The disk uses isolinux. Is there a "package" for problems with the CD?

My bad, thanks for pointing this out. :)

Try pressing F6, then escape and enter nomodeset into the boot options. You can also refer to this http://www.ubuntugeek.com/how-to-fix-ubuntu-10-04-lts-lucid-blank-screen-at-startup.html

And nomodeset is actually on the menu you get if you hit F6 twice.

The "safe graphics mode" was deliberately removed, because:

revno: 1528
committer: Colin Watson <email address hidden>
branch nick: debian-cd
timestamp: Fri 2010-02-12 13:11:00 +0000
message:
  remove "Safe graphics mode" menu entry; xforcevesa no longer has any effect, ubiquity-dm now handles VESA fallback, and we'll handle nomodeset a different way

So I don't know that there's much more we can do about this. Modesetting bugs really do need to be fixed in the kernel anyway - we'll be relying on this more and more as time goes on, so calling it "safe graphics mode" would be a bit inaccurate I think.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in ubiquity.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

I would like to share the solution I've used.

If you add the options "nomodeset single" before the "--" in the installation boot options, the boot process will end in a choice screen in which one of the options is: Start failsafe X session.

I hope it helps.

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 671711

and any other logs that are relevant for this particular issue.

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]