Closed Bug 813979 Opened 13 years ago Closed 13 years ago

Keyboard not working with Firefox 17 on Windows XP SP3

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
17 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mozilla, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 Build ID: 20121025231724 Steps to reproduce: Upgraded form FF 16 to 17.0. Actual results: FF now ignores most keyboard input. This happens in both the chrome and pages, i.e. no text can be typed in URL bar, search box, text inputs, 'Password required' popup, etc. The Tab and Return keys are still working, however. No other app has a keyboard problem, so it comes from FF. It still happen with all extensions and plug-ins disabled, in safe mode, and after a reboot.
Severity: normal → major
OS: Linux → Windows XP
Hardware: x86_64 → x86
This report is for Windows XP ? You have SP2 installed ? In that case : works for me with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0
SP3, actually. I am entirely certain it works on some/most XP machines, otherwise a QA engineer needs a stern talking-to. I would not know what information about the system to give, though, so if someone tells me what is needed I will be happy to provide it. All I can say for now is FF 16 works -> upgrade from popup -> FF 17 does not work.
Did you try it in the windows safemode ? That should disable all third party software that could be unique to your system. I see only one other chance: A regression range search to find the changeset that triggers the issue on your system. We have a tool that helps with this task but requires some work: https://github.com/mozilla/mozregression#readme e.g. "mozregression --good=2012-04-01"
Good call, it works in Windows safe mode. It now also works after booting in normal mode. I had rebooted and tested earlier today, so it seems to have been the passage through safe mode that did it; I can't even begin to imagine what the problem can be. Closing the ticket since I can't reproduce the problem anymore. Thanks, Matthias.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
strange...
You need to log in before you can comment on or make changes to this bug.