From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.6) Gecko/20050309 Fedora/1.7.6-0.cvs.20050309 Description of problem: There are no key events from the right "windows" key. If I on a virtual console run "showkey -s", nothing is printed when I press the right hand "windows key". Version-Release number of selected component (if applicable): kernel-2.6.11-1.1226_FC4 How reproducible: Always Steps to Reproduce: 1.Run showkey -s 2.Press right hand side "windows key". Actual Results: Nothing Expected Results: Some scan codes Additional info: I'm using a Swedish keyboard. /etc/sysconfig/keyboard has KEYBOARDTYPE="pc" and KEYTABLE="sv-latin1". It worked fine with FC3 and older kernels. I suspect this bug could be the underlying reason for the problems I reported in bug 154448. With xev this key reports mouse events. But I know too little about how X do things so I'm not sure, and report it separately.
I'm confirming this behavior with FC4 final. Running 'showkey -s' does not record it when the right windows key is pressed. The left windows key is recognized however. In X Windows (KDE/Gnome), xev reports the key as mouse button 4 (scroll up).
Mass update of -test bugs to update version to fc4. (Please retest on final release, and report results if you have not already done so). Thanks.
Kris Ven had already confirmed it in FC4 final in comment 1. Now I too have tested it there, with all patches applied. The bug is still there.
After installing kernel-2.6.12-1.1387_FC4 the problem appears to be gone. The key shows up with shwokey, and also behaves correctly in X again.
I cannot confirm whether the new kernel (2.6.12-1.1387_FC4) solves the problem, since it kernel panics on boot up. I'll have to file/search a separate bug report for that first. I'll report on this bug, once I got the new kernel working.
I've verified some more (on i386 and x86_64), and am convinced this is solved with the 2.6.12 kernel. If you should find otherwise Kris Ven, reopen. (Or file a new.)
*** Bug 154448 has been marked as a duplicate of this bug. ***
I installed the kernel on a different machine on which the kernel *does* work, and the problem has disappeared. This bug has indeed been solved.