Summary: | Multimedia keys not recognized event though correct layout is selected (Dell Latitude series laptop) | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | MartinG <gronslet> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kde, peerit |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
MartinG
2008-08-16 16:47:34 UTC
The problem with my KDE 4.1 and the media keys on my keyboard was that alle the XF86Audio* were declared twice as I saw in "xmodmap -pk | grep -i audio" output: 159 0x1008ff14 (XF86AudioPlay) 0x1008ff31 (XF86AudioPause) 160 0x1008ff12 (XF86AudioMute) 161 0x1008ff1d (XF86Calculator) 162 0x1008ff31 (XF86AudioPause) 163 164 0x1008ff16 (XF86AudioPrev) 165 166 0x1008ff12 (XF86AudioMute) This is just an extract. Like you can see AudioMute is set twice but KDE recognizes only the first value. I know that because my key for mute has the code 160 and the keys on my keayboard vor volume up/down have the latter/higher codes and so are not functional. FWIW, this is what I get: $ xmodmap -pk | grep -i audio 144 0x1008ff16 (XF86AudioPrev) 153 0x1008ff17 (XF86AudioNext) 160 0x1008ff12 (XF86AudioMute) 162 0x1008ff14 (XF86AudioPlay) 0x1008ff31 (XF86AudioPause) 164 0x1008ff15 (XF86AudioStop) 0x1008ff2c (XF86Eject) 174 0x1008ff11 (XF86AudioLowerVolume) 176 0x1008ff13 (XF86AudioRaiseVolume) Just to add to the above, I sometimes have to "kickstart" the Win-key by running "setxkbmap -option 'win:meta'" in an terminal (as normal user). Works for me now in KDE 4.1.96. MartinG ? Does it work for you too? If yes please close this bug. All special keys seems to work now: Volume up, volume down and mute (these also gives OSD info), brightness keys does not give OSD, but works as expected (as they always have), stand-by button works. The hibernate button (Fn-F1) does nothing (I haven't configured it to do anything either), and the battery button (Fn-F3) does nothing, but I guess I could configure these. None of the special keys report unrecognized keypresses (dmesg) anymore, so I guess this is fixed, therefore closing this bug. Thanks! Note, however, that what I would really like to have, is a simple user friendly tool with which I could record and report all multimedia keys back to the KDE team, for easy inclusion in the next release. That way I, as a non-developer, could help other users get stuff to work out of the box with "new" hardware. (The Dell Latitude X1 is old and outdated and is barely able to run KDE4 anyway, so I will probably have to buy a new laptop soon, and go through the multimedia key hassle all over) This is using: kernel 2.6.28 (Linus git ede6f5aea054d3fb67c78857f7abdee602302043, newest suspend/resume working kernel for the X1) kdelibs-4.2.0-11.fc11.i386 |