In GUI installer for beta1 release I provoked an error in a boot
floppy creation by simply choosing to do that and _not_ putting a
floppy in a drive (but this could be a bad floppy or an honest
mistake). Anaconda prompty died and it stopped to react on any
keyboard or mouse input. After switching to text consoles and back a
screen image was also not updated (a general outline was still present
on a monitor). No traceback, no messages, no recorded errors; just a
silent death. I was able to finish an installation "manually", from a
command line, but for a newbie all work up to this point would be
Please verify in test lab.
hmmm ... I could not verify this using beta1 or beta2 ...
Are you getting this behavior in beta2 ...? Any error messages on the VCs ...?
*** Bug 12420 has been marked as a duplicate of this bug. ***
I'm closing this as we can't reproduce it. *Please* try again w/ beta 3, and
repoen this bug if
it's still happening. Every time we try this, it works properly <sigh>.
I tested on rh70. GUI.
I put a floppy in, but it seems it had some bad sectors so that vt4 was full of
i/o errors. anaconda went on for a lot of time this way, frozen.
Then it said "there is a problem on the boot disk...", I took out the disk and
clicked "go on", thinking it would skip the boot disk, but it tried again (I
didn't check "skip..") and this time there was no boot disk in the floppy
drive. anaconda didn't understand this and tried hard to create the boot disk
(vt4 full of i/o errors), I had to wait for about 10 minutes before anaconda
gave up, then I chose to skip the boot disk phase and I could complete the
I think you should do a quick test to see if the floppy is actually in.