Created attachment 437790 [details]
Description of problem:
It sometimes happens that that graphical installer stops at the point where the first fedora graphical window appears: But pressing the "next" button shows no reaction (so as it would be insensitive). The only way to proceed is using the TAB key, navigating to the "next" button and pressing the "enter" key.
But in the most cases, a can press "next", and it proceeds.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot the F14/RC2/alpha dvd without any parameter
I can operate with the mouse
My box has an USB mouse, but the same happens, if connecting that USB mouse via a PS2 adapter.
I will attach /tmp/X.log, /tm
Created attachment 437791 [details]
Created attachment 437792 [details]
lspci -vv output
This sounds like the same bug:
Bug 632431 - gui installer next / previous buttons need immediate feedback
I'm seeing this exact same problem. If I use "vesa" mode, the mouse works. I booted the DVD six times. Three of the times I did the "default" graphical install and the mouse clicks didn't work. The three times that I booted in "vesa" mode, the mouse worked just fine. If you can tell me what logs/info you need, I'll be happy to collect it.
I'll attach my lsusb and lspci output (from my machine booted as FC13) as watzkej-lsusb.txt and watzkej-lspci.txt so you can see my hardware.
Created attachment 448495 [details]
watzkej_lspci -vv output
Created attachment 448496 [details]
watzkej_lsusb -vv output
Created attachment 448508 [details]
tar file with /tmp/X.log and other anaconda logs
I may be seeing this too.
With the F14-Beta-RC1 net installer CD, sometimes the graphical installer does
not respond to mouse clicks.
I haven't found a reproducer, but in two trials the first graphical display
would not respond to clicks on the Next button. Attached logs are for this
When this problem occurs, a workaround is to use Tab and Enter, to which the
installer responds immediately.
Installer CD tests OK.
USB wired mouse works normally.
Graphical pointer is responsive.
(Copied from Bug 632431, Comment 1)
(In reply to comment #5)
> I'll attach my lsusb and lspci output (from my machine booted as FC13) as
> watzkej-lsusb.txt and watzkej-lspci.txt so you can see my hardware.
They may also want to see /tmp/X.log from when you are in the installer and the problem occurs.
Created attachment 448694 [details]
anaconda.log from Steve's tarball
Created attachment 448695 [details]
program.log from Steve's tarball
Created attachment 448696 [details]
storage.log from Steve's tarball
Created attachment 448697 [details]
syslog from Steve's tarball
Created attachment 448698 [details]
X.log from Steve's tarball
Same issue with F14/Rc3/beta.
*** Bug 632431 has been marked as a duplicate of this bug. ***
not sure what the right resolution here is but F14 alpha/rc2 is even more EOL than F14 :)