View Full Version : Strange Keyboard problems..WIN key doesnt work
aniketv
2006-05-28, 05:38 AM CDT
I use KDE as my desktop.
I have assigned a few global shortcuts in AmaroK which use the WIN key.
When I boot my PC , sometimes these shortcuts do not work as the WIN key is somehow not recognised. Then I play around with the "keyboard layout" section in Kcontrol and it starts working ... The strange thing is that I selected "Generic 102 key "(that was selected by default) model for my keyboard . Then when it doesnt work , I just change to something else ( anything !!) hit "apply" ..then again select "Generic 102 key" , the WIN key starts to work . I amat my wits end trying to find out the problem. Please help..
This problem did not exist in fedora core 4 previously, I am facing it only in FC5.
aniketv
2006-05-30, 04:50 AM CDT
Please help people ...I know its a weird problem..but please...to all the Linux Gurus
InKo
2006-05-30, 06:19 AM CDT
actually I have no idea why that happend but I would firstly see in
/etc/sysconfig/hwconf and /etc/sysconfig/keyboard ...
aniketv
2006-05-30, 06:27 AM CDT
in hwconf it this..
class: KEYBOARD
bus: PSAUX
detached: 0
desc: "AT Translated Set 2 keyboard"
And in /etc/sysconfig/keyboard
KEYBOARDTYPE="pc"
KEYTABLE="us"
I have a generic multimedia keyboard by a brand called Tech-Com ..its a local brand.
Can you tell me what to change?
But a what I dont understand is , just by playing around with the keyboard layout options in KControl, it gets fixed. I think the problem may lie with KDE too..any ideas.
InKo
2006-05-30, 06:38 AM CDT
in hwconf it this..
class: KEYBOARD
bus: PSAUX
detached: 0
desc: "AT Translated Set 2 keyboard"
add:
driver: ignore
aniketv
2006-05-30, 08:59 AM CDT
Thanks ..I will post back my results
EDIT: That did not help . The problem still persists.
Any other solutions..??
clue
2006-06-21, 10:53 AM CDT
I'm having also the same problem. This is definitley a FC5 bug. Hope this will be fixed soon.
InKo
2006-06-22, 02:34 AM CDT
yep, it seems to be that... :(
grepsy
2006-06-23, 01:12 PM CDT
If you run the command
xev
and get the key code you can then put the following line in your .Xclients-default
xmodmap -e "keycode ### = XF86****"
where ### is the keycode number from xev and **** is from one of these in the list. You don't have to match it up directly as long as you press that key after restarting X to set it in amarok or KDE
The list of XF86 codes can be found here
http://wiki.linuxquestions.org/wiki/XF86_keyboard_symbols
icydog
2006-06-23, 04:04 PM CDT
I have had this problem on both my FC5 machines too. This problem is very stupid and should not exist. Here's what I did to fix it:
1. Open KDE Control Center
2. Regional & Accessibility -> Keyboard Layout
3. Go to the Xkb Options tab and scroll down
4. Under "Alt/Win key behavior" select "Super is mapped to the Win-keys (default)."
Why you have to explicitly pick a default option is beyond me. I always thought default meant default. Oh well. I hope I helped.
Caesar Tjalbo
2007-06-14, 03:34 PM CDT
I have had this problem on both my FC5 machines too. This problem is very stupid and should not exist. Here's what I did to fix it:
1. Open KDE Control Center
2. Regional & Accessibility -> Keyboard Layout
3. Go to the Xkb Options tab and scroll down
4. Under "Alt/Win key behavior" select "Super is mapped to the Win-keys (default)."
Why you have to explicitly pick a default option is beyond me. I always thought default meant default. Oh well. I hope I helped.
Worked for me. Thx!
Bachmann
2007-06-24, 02:27 AM CDT
is there anything that can be done if you do not use kde? (XFCE user here)
vBulletin® v3.8.1, Copyright ©2000-2009, Jelsoft Enterprises Ltd.