Description of problem:
clicking reboot at the end of the install does nothing.
Version-Release number of selected component (if applicable):
Language = French
Will try again in English to see if this is dependent on the
Steps to Reproduce:
1. TUI install
2. proceed through all screens
3. click "Redemarrer" on final screen
4. Nothing happens
I've seen this sporadically... unfortunately, I haven't quite tracked
down what the circumstance that causes it is :/
*** Bug 119171 has been marked as a duplicate of this bug. ***
Performed this in English, on a Digital Celebris Pentium Pro 180, with
64MB of RAM, and it refused to reboot, in spite of clicking Enter
Bug 119637 is a duplicate of this bug as well, so please mark it as such.
*** Bug 119637 has been marked as a duplicate of this bug. ***
*** Bug 120617 has been marked as a duplicate of this bug. ***
I have also seen this bug. I do not use a mouse at all, and have found
that the return key has not effect even if pressed repeatedly. BUT if
another key e.g. space,a,b etc is pressed first and then the return
key is pressed the reboot occurs correctly.
Ben -- do you have a consistent reproducer for this? Like I said, I
see it "sometimes", and that's making it a bit difficult to debug :)
I met this bug almost everytime when I install RHEL4_Alpha2 releases
in ia32 platforms.
Has anyone seen this recently?
This does not happen on my Digital Celebris any longer, with the FC2
test3 CDs. So, this could possibly have been fixed with the latest
*** Bug 123120 has been marked as a duplicate of this bug. ***
I am still seeing this in FC2T3(also happened in T2 and T1).
Machine is an XCcube with a UX4SG-1394(EZ65) motherboard(Intel 865G
chipset) and a 3GHz Pentium 4.
Pressing space before return gets the reload to work.
Could a message could be added indicating that if enter alone does not
work that the user could try pressing space first?
How's it going with FC2 install itself Jeremy Faith (comment 12)?
Seems to workforme, and no one else has really complained about this
bug in a while...
Should be fixed in the final, I figured out what was causing it and
put in the fix.
Yes, this is now fixed on the XCube, thanks.
Sorry it took so long to respond but the machine was away at a demo
for a while.
I'm seeing this on a zx1 HP machine with the re0721.0 tree via serial
Is this happier now?
Hasn't been seen in a while, closing.