Bug 8731
Summary: | Numlock light gets off after hibernation | ||
---|---|---|---|
Product: | Drivers | Reporter: | Victor Porton (porton) |
Component: | Input Devices | Assignee: | Rafael J. Wysocki (rjwysocki) |
Status: | CLOSED INVALID | ||
Severity: | normal | CC: | bunk, mszpak |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.21.5 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 7216 |
Description
Victor Porton
2007-07-10 07:12:45 UTC
Does it work properly if you start hibernation while in text console as ooopsed to being in X? I can reproduce it on similar hardware. If hibernation is started from a text (FB, to be precise) console, the keyboard works properly (ie. the numlock status is restored). So, are we going to do anything about it? I need to finish moving LED handling into generic resume in input core. That will ensure that all keyboards work the same way. However X manages LED state outside of kernel and so we can't really do anything... And X is very stupid - it does not properly restore LED state if you hit CapsLock and switch to a text console and back. I know that the kernel is working because LED state is restored properly if you switch between text VTs. So, this is not a kernel bug, but an X problem. I think we should close this entry, then. I think the numlock restore still does not work for USB keyboards so closing it is premature. OK, sorry. Should I reopen? |