Bug 8035
| Summary: | Win + <somekey> (global) shortcuts don't work in KDE | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Artem S. Tashkinov (aros) |
| Component: | Input Devices | Assignee: | drivers_input-devices |
| Status: | REJECTED INVALID | ||
| Severity: | high | ||
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.22 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: |
xev and kernel .config
config files from Fedora Core my 2.6.23 kernel configuration |
||
Created attachment 10454 [details]
xev and kernel .config
xev output under different kernels and my 2.6.19 and 2.6.20 .configs
That excerpt of xoorg.conf that you posted - is it your personal modification or FC6 standard config? > That excerpt of xoorg.conf that you posted - is it your personal modification
or FC6 standard config?
It's a FC6 standard config, except Xleds option.
I want to pronounce it once again:
1) under FC6's kernel everything works fine with the same X.org configuration
(X.org 7.1)
2) under _my_ kernel X.org 7.0 (FC5) everything works fine
You may take my config as an example and run xev yourself (in X.org 7.1, of
course). This bug is easily reproducible.
I have filed this bug into freedesktop's bugzilla as well, but there's no any
kind of response.
Does it work if you enable evdev in your kernel? Does it work when you recompile vanilla 2.6.20 with redhat's .config? grep -i evdev /usr/src/linux/.config CONFIG_INPUT_EVDEV=m lsmod | grep evdev evdev 7616 3 Where can I find a sample FC's .config? src.rpm has so many files - I cannot figure out which one is the final configuration. Oh, I see. What is .config-2.6.19 in your info tarball then? As far as FC6 config goes - you will either have to figure out from their rpm spec file or just ask redhat. > Oh, I see. What is .config-2.6.19 in your info tarball then? For your pleasure: you might want to compile 2.6.19 kernel. Now I'm running 2.6.20 > As far as FC6 config goes - you will either have to figure out from their rpm spec file or just ask redhat. I have read and understood the underlying logic of their spec file - I'm compiling 'FC6' kernel right now. Created attachment 10474 [details]
config files from Fedora Core
1) I have compiled kernel 2.6.20 with Fedora Core 6 .config file and Win key
still doesn't function properly (i.e. when I press it alone - it works, but key
combinations don't work)
2) Under kernel-2.6.19-1.2911.fc6.i686.rpm everything works fine
config-2.6.19-1.2911.fc6 is extracted from kernel-2.6.19-1.2911.fc6.i686.rpm
config-2.6.20-fc6 is generated by me from fedora core 6 cvs repository
Dmitry, have you actually investigated my .config file? Did you find anything wrong with it? FC's CVS of linux kernel is located here: http://cvs.fedora.redhat.com/viewcvs/devel/kernel/ Artem, Your .config seems to be fine. I also looked at the FC kernel repo but did not see any patches that I would consider as "interesting" WRT your issue. xev logs that you presented show that both kernels first emit scancode what X recognizes as Super_L but on your kernel nobody "grabs" the focus. I'd recommend asking on X mailing lists how to debug this kind of problem. Dmitry, If I understand you correctly you're saying it's rather an X.org bug not a Linux kernel bug. Right? Still, why Xorg works perfectly well under FC's custom kernel? It seems to be a mystery for me. No, I am not saying that this is necessary a X vs. kernel bug, but we need help from X and/or KDE people to figure it out. The kernel delivers what X believes to be Super_L in both cases (as your xev logs show). However, for some reason, on custom-compiled kernel KDE instead of grabbing focus does nothing. X.org developers silently ignored my message to their mailing list. Dmitry, can you repeat this bug mystery? I mean do you see xev generating different events with different kernels? I'll try to play when I get home tonight, however I am using FC3 so it will be older versions of X/KDE. Works for me here on 2.6.20+, xorg 6.8.2 and kde 3.5.3 Do you mean my .config works for you? Alas, I'm running X.org 7.1 and X.org <= 7.0 doesn't have this bug. X.org developers seem not to care about this bug but it's still here. Fedora 7/X.org 7.3/X Server 1.3/Vanilla kernel 2.6.22 Ok, now that I upgraded to Fedora 7 I tried reproducing it again and I still can't. I tried with kde-3.5.7, 2.6.23-rc9 and whatever version of X Fedora has at the moment. I can post my 2.6.22 .config again so that our kernel configurations match. Anyway I have found two more people who have the same problem (fedora kernel works, vanilla kernel doesn't). Created attachment 13113 [details]
my 2.6.23 kernel configuration
The bug persists :-(
Here is my 2.6.23 kernel configuration - please, adjust it for you PC.
This bug is reproducible with a default Fedora 8 installation with all updates applied. The relevant XFree bug is located here: https://bugs.freedesktop.org/show_bug.cgi?id=8815 Since some XFree applications can perfectly grab Win + other_key combinations I think it's worth closing the bug. Under yet not known circumstances this bug has gone away. With vanilla KDE 3.5.9, xorg-x11-server-Xorg-1.3.0.0-42.fc8, kernel 2.6.25.3 everything works fine. The bug is here again with 2.6.26 ;-) Sorry for flooding - in fact everything works find with 2.6.26. |
Most recent kernel where this bug did *NOT* occur: not known Distribution: Fedora Core 6 Hardware Environment: PS/2 standard 105 keys keyboard Software Environment: X.org 7.1 Steps to Reproduce: 1. Open Control Center -> Regional and Accessibility -> Keyboard Shortcuts 2. Select Windows Scheme with Win Key -> hit Apply 3. Try to use any global shortcut with Win key Actual results: Nothing happens, KDE ignores all shortcuts with Win key Expected results: Keyboard shortcuts with Win key work When you try to assign a key combination with Win key to any Action, e.g. <Win> + <R> for "Run a Command" then only "R" gets entered. Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us,ru(winkeys)" Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll" Option "Xleds" "1 2 3" EndSection After some investigation I've understood that my custom kernel is to be blamed for such a behavior. Somehow it's very strange because with the same kernel .config-uration FC5 _worked_ fine (with X.org 7.0). ***Most important information concerning this bug***: Under two kernels: Fedora Core's one and mine xorg xev application generates different output. The bug is also posted here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213017