Bug 54385

Summary:	keyboard config broken for SPARC LINUX w/ sun5 keyboard
Product:	[Unmaintained] kcontrol	Reporter:	Razathorn <raz>
Component:	kcmkeyboard	Assignee:	Patrick Dowler <dowler>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	ana
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Razathorn 2003-02-10 07:54:30 UTC

Version:            (using KDE KDE 3.1)
Installed from:    Compiled From Sources
Compiler:          gcc -2.95.4 sparc linux
OS:          Linux

fresh sparc linux install with a sun type 5 keyboard on an ultra60:

Keyboard's 'b' key does not work after kde is loaded.  Works great in windowmaker and in kdm's login dialog.  I have tried selecting the sun5 variant.. but when I exit the dialog and come back, it has been switched back to pc104 etc.

The b key acts like a modifer of some sort... in a terminal, after pressing the b key, all other keys produce new and interesting characters which really make bash angry.

Comment 1 Razathorn 2003-02-13 09:07:08 UTC

Figured out what was going on.  Aparently on sparc linux, the 'b' keycode and the 
'print' key code are getting 'mixed up' or something to that effect.  I found that when I 
choose the Windows keyboard shortcuts with 'win' key, screen shot is bound to the 
print key.  This was the offender.  As soon as I remove the print key binding, things 
started working fine.  Additionally, when you try to assign 'shift-print' as the keystroke, 
it ends up being captured as 'shift-b'.  Hope this helps.  For now, I am getting by 
without the print key bound to anything.

Comment 2 Riku Voipio 2004-03-10 22:00:25 UTC

A debian user seems to have the same problem:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=235684

"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."

Comment 3 Philip Rodrigues 2007-03-08 22:27:45 UTC

Does this problem still occur with KDE 3.5?

Comment 4 Philip Rodrigues 2007-04-30 22:57:20 UTC

Feedback timeout, but please reopen if the problem still occurs in KDE 3.5. Thanks!