AmigaPhil@ping.be wrote:
ken (gebser@speakeasy.net) wrote something I wish to comment : (news:<42AF6BC8.4090107@speakeasy.net> posted on 15-juin-05 00:44:08)
My keyboard problem is still not fixed. I received some feedback
from the Suse support team, but with no help so far.
I haven't been able to re-install the xorg package (or install a new one which may contain the bug fix I'm hunting ?). Any help welcome.
Can someone who is using the Suse 9.3 distribution with a working AZERTY keyboard (preferably a Belgium layout, but other may help too) send me his /etc/X11/xorg.conf file for me to compare ?
In your /etc/X11/xorg.conf find the:
Section "InputDevice" ... EndSection
that describes your keyboard.
Somewhere inside of that (I don't think it matters where), insert
Option "XkbLayout" "be-latin1"
Sounded good to me. That line was
Option "XkbLayout" "be"
and I change it to:
Option "XkbLayout" "be-latin1"
then reboot the computer... No change :-(
I did perform the same change to /etc/X11/xorg.conf-Linux1 (where "Linux1" is the name of my machine) and reboot. No change either.
Strange crap! Do you have /etc/X11/xorg.conf or just the xorg.conf-Linux1 file? If there's no xorg.conf, copy the xorg.conf-Linux1 to xorg.conf. Then just do Ctrl-Alt-Backspace; you don't need to reboot. I forgot to mention in my previous post that the keyboard can be configured in the file /etc/sysconfig/keyboard (also). Near the top of that file you'll find a variable called KEYTABLE; set that to "be-latin1.map.gz". You might want to check through /etc/sysconfig/language also, to make sure the settings are correct there too. If it still doesn't work after these changes, check the date/time on your /var/log/Xorg.0.log. If the date/time corresponds to the last time you loaded X or after, cut-n-paste that into your next reply so we can have a look at it.
In another reply on this list, Carlos E. R. suggested that the keyboard problem might be due to a bug in KDE (someone else on the Spanish list reporteing about the same problem).
That's possible. I doubt, though, with all the people around the world using Linux, including developers, that there's a major bug in non-US keyboard configuration. Of course, since I don't use that, I can't really make first-hand comments.
Indeed, when I switch back to runlevel 3 ("init 3" from a console) and test the keyboard from the console, it is working fine (I can print the missing e acute and aroba).
That's good, but it doesn't help us at all here. The keyboard configuration for levels 3 and 5 are completely different subsystems.
So maybe my keyboard problem IS due to a bug in KDE (?), and not to a misconfiguration of xorg as I thought.
I'm using gnome. That might make invalid at least some of what I've been recommended, not sure either way. Are you really wedded to KDE?
Still searching...
Thanks for your help.
Well, we still don't have it working for you. So, the next time I'm in Belgium you can loan me your non-working car. -- A lot of us are working harder than we want, at things we don't like to do. Why? ...In order to afford the sort of existence we don't care to live. -- Bradford Angier