On Tuesday, June 08, 2010 03:55:08 pm Éric Piel wrote: > Op 08-06-10 11:33, Éric Piel schreef: > > Hello, > > I haven't investigated much yet, but I have the feeling that since > > 2.6.35-rc1 my "Print Screen/SysRq" key works only as SysRq: if I press > > it (normally assigned to take screenshot in gnome), nothing happens (no > > input event received in userspace) and no key on the keyboard works > > afterwards, until I press Alt. Actually the keys work, but behave as if > > the sysrq key was kept pressed (can be seen in dmesg, or by pressing > > "b"). > > > > Looking at the log, a potential culprit is commit > > 97f5f0cd8cd0a05449cbb77d1e6f02e026875802 (Input: implement SysRq as a > > separate input handler). Probably the logic of "have to press all the > > keys at the same time" changed to "have to press the keys one after each > > other". So pressing alt and later on pressing PrintScreen leads to a > > SysRq. > > > > Does anybody else see this behaviour? Any suggestion on how to solve > > this bug? I'll try reverting the commit and report if it fixes the > > problem (the git revert fails so I've got to fix the conflict manually). > > I can confirm this regression is due to > 97f5f0cd8cd0a05449cbb77d1e6f02e026875802: the reverting patch below > fixes it. And, as long as you don't press alt since boot, PrintScreen > works fine. So it is likely due to not taking into account key releases. > > Dmitry, do you have a better fix? I'll be happy to test it if needed. > Not yet, but I see the effects you are describing... Stay tuned... Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
