1073322 - version 32.0.2 stops mouse and keyboard from working

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[sijae]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140917194002

Steps to reproduce:

my pc downloaded and updated to version 32.0.2. when i rebooted the pc, my mouse and keyboard stopped working.


Actual results:

i had to go back to a restore point before the update and the mouse and keyboard work again. i had repeated this 5 times with the same results. i made sure not to download anything else (no windows updates).


Expected results:

i expected everything to work as normal once i downloaded the lastest version of firefox.

Comment 1

[Stefan Weiss [:sir_none]]

Hello,
can you give us more information about it? I was not able to reproduce it.

- is mouse and keyboard blocked overall? or just in Firefox?
- is the issue still existing with Firefox update 32.0.3?
- if the isue is just in firefox itself, can you try to start in safe mode?
https://support.mozilla.org/de/kb/firefox-probleme-beheben-abgesicherter-modus

Comment 2

[sijae]

my keyboard is a Logitech G15 and the mouse is a Razer Lachesis 5600.

i did another test and i found that it was not really the mouse. the USB ports on the back of the PC no longer worked. other USBs located on the top of the PC did work. i again reset to a different save point and the USB ports on the back of the PC worked again.

Comment 3

[Stefan Weiss [:sir_none]]

Hello,

please give answers to my questions. specialy 2 and 3 would be nice to know.
thanks for all your help to make firefox better.

Comment 4

[sijae]

hello,

i have tried the recent update to firefox 32.0.3. the issue is no longer there!

as for safe mode, i did not even try safe mode. i only did resets to a save point that did not have the issue with the USB ports not working.

Comment 5

[Stefan Weiss [:sir_none]]

Hello,

first of all - good to see that it is Ok in actual version.
I have checked all other open reports since Version 32.0.2 and there was no other case like this.

it is not possible for us to reproduce, so I hope you are OK with my decision to close this bug.