| View previous topic :: View next topic |
| Author |
Message |
Batsi
n00b
Joined: 30 Mar 2004
Posts: 13
Location: Munich, Germany
|
 Posted: Tue Jul 12, 2005 10:29 pm Post subject: [solved] Keyboard on Ultra5 won't "b" with KDE |
 |
|
Hello,
I got a Sun Ultra5 successfully running with gentoo, but now I have problems with my non-USB type6-keyboard on xorg.
Almost every key works except the "b". This is the keyboard part of the xorg.conf:
| Code: | Section "InputDevice"
Identifier "Keyboard1"
Driver "keyboard"
Option "Protocol" "Standard"
Option "XkbKeyCodes" "sun(type5)"
Option "XkbModel" "type5"
Option "XkbRules" "sun"
Option "XkbLayout" "us"
Option "XkbTypes" "types/complete"
Option "XkbCompat" "compat/complete"
Option "XkbGeometry" "sun(type5unix)"
EndSection |
On the text console everything's working fine.
To isolate the reason for this I tried "xev" while running X.
Pressing "b" gives out the following: | Code: | FocusOut event, serial 30, synthetic NO, window 0x400001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 30, synthetic NO, window 0x400001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 30, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 4294967168 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 30, synthetic NO, window 0x400001,
root 0x38, subw 0x0, time 95718, (111,-18), root:(909,5),
state 0x0, keycode 111 (keysym 0x62, b), same_screen YES,
XLookupString gives 1 bytes: (62) "b" |
Just for comparison, pressing "n" gives out this: | Code: | KeyPress event, serial 30, synthetic NO, window 0x400001,
root 0x38, subw 0x0, time 96130, (111,-18), root:(909,5),
state 0x0, keycode 112 (keysym 0x6e, n), same_screen YES,
XLookupString gives 1 bytes: (6e) "n"
XmbLookupString gives 1 bytes: (6e) "n"
XFilterEvent returns: False
KeyRelease event, serial 30, synthetic NO, window 0x400001,
root 0x38, subw 0x0, time 96199, (111,-18), root:(909,5),
state 0x0, keycode 112 (keysym 0x6e, n), same_screen YES,
XLookupString gives 1 bytes: (6e) "n |
I don't understand why pressing "b" only results in a "KeyRelease" and no "KeyPress".
The funny thing is: "B" (upper case) is working. But at least this is not Windows and therefore there's a huge difference between a "b" and a "B".
btw, "Ctrl-Alt-Fn" doesn't work for changing the console either.
I tried a few other configurations for xorg, but the one posted above is the only one almost every key resulting in the right letter.
Perhaps someone knows about this problem, or has at least a possible method of resolution.
Last edited by Batsi on Thu Jul 14, 2005 9:02 pm; edited 1 time in total |
|
| Back to top |
|
 |
simon_6162
n00b
Joined: 07 Jul 2005
Posts: 8
|
| Posted: Wed Jul 13, 2005 4:51 pm Post subject: Re: Type6-Keyboard on Ultra5 won't "b" |
|
|
| Quote: |
KeyRelease event, serial 30, synthetic NO, window 0x400001,
root 0x38, subw 0x0, time 95718, (111,-1 , root:(909,5),
state 0x0, keycode 111 (keysym 0x62, b), same_screen YES,
XLookupString gives 1 bytes: (62) "b"[/code]
|
Hi this part is sending the right keycode (111) so thats good, however the top part seems to imply that this key is also mapped to somthing else.
open /usr/lib/X11/xkb/keycodes/sun in a text editor as root
do a search for 111
The only lines containing 111 should be assigned to the key " <AB06> = 111" if you find any other key assigned to the same number comment it out with a "//".
Also /usr/lib/X11/xkb/symbols/sun/us is a list of key codes and how they map to symbols. e.g <AB06> = b, |
|
| Back to top |
|
|
chance2105
Tux's lil' helper
Joined: 10 Jun 2004
Posts: 112
Location: Norman, OK USA
|
| Posted: Thu Jul 14, 2005 2:52 pm Post subject: |
|
|
Batsi: are you running KDE perhaps?
Although possibly unrelated, I've seen that exact same issue happen while running KDE, but _not_ running other DE's on the same box.
No lower-case 'b' but uppercase 'B' .. |
|
| Back to top |
|
|
Batsi
n00b
Joined: 30 Mar 2004
Posts: 13
Location: Munich, Germany
|
| Posted: Thu Jul 14, 2005 6:48 pm Post subject: |
|
|
| chance2105 wrote: | | are you running KDE perhaps? |
Yes, in fact I do. So I googled for this and found the following:
http://bugs.kde.org/show_bug.cgi?id=54385
| Quote: | "It looks like the 'b' problem only occurs when the keyboard shortcuts
are set to "Windows Scheme (With Win Key). Removing the print shortcut
didn't do it, but switching to any other scheme seems to fix it. xev
now reports the correct events." |
But I don't really understand. Where have I set my keyboard shortcuts to "Windows scheme"? |
|
| Back to top |
|
|
Batsi
n00b
Joined: 30 Mar 2004
Posts: 13
Location: Munich, Germany
|
| Posted: Thu Jul 14, 2005 8:53 pm Post subject: |
|
|
| Batsi wrote: | | But I don't really understand. Where have I set my keyboard shortcuts to "Windows scheme"? |
After reflecting about it, I finally got it. Look here: bbbbbbbbbbb 
For everyone who's as obtuse as me:
KDE Control Center -> Regional & Accessibility -> Keyboard Shortcuts
I changed the "Current Scheme" which was probably the "windows scheme" to "UNIX Scheme" and now everything's great.
Although I still can't use "Control-Alt-Fn" to get my text console back again. But now the main problem is solved.
Thanks for the tip with KDE, this was the hint I needed. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on Sparc
