9.3: Keyboard keymaps and xorg
I'm still trying to fix the configuration problem of my keyboard (BE keymap). I'm now suspecting a mess in the xorg-x11 installation (file missing or such, as were the xorg docs and man pages), so I tried to re-install the xorg-x11 core package (using yast). This too failed (someting related to permission denied). Is this due because the x-server is already running ? How can I install the xorg-x11-6.8.2-30.i586.rpm from a command line (or prior the x-server is running) ? AmigaPhil, world citizen. _No MS-HTML mail please_ PGP key: 0x9C07F6C1 -----BEGIN ECHELON TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. AppLyYkjvMcEpVvzByIS6ttFCOHOFaDObyHnpnyyVjREK3znMRHUlStROD5EMEtvzVTHFh1p aEOSlrcxOJIIAOplSxSIDVyaVPAvOAlFtVqDHDz1GtzKVDVJaDvHFqtHMyRvzdW0xtGVBy5t JM5JFWaOOzWFHlWOoIpvFTFIIqUU0EIxRJLLyUpUlb2VqRlIdMEtOHVtV5NMzfFHVIRqHuPv vM3tGO -----END ECHELON TEASER----- Don't look at me! I'm A Generic Tagline
I'm now suspecting a mess in the xorg-x11 installation (file missing or such, as were the xorg docs and man pages), so I tried to re-install the xorg-x11 core package (using yast). This too failed (someting related to permission denied).
Is this due because the x-server is already running ? How can I install the xorg-x11-6.8.2-30.i586.rpm from a command line (or prior the x-server is running) ?
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 ? Thanks. AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN ECHELON KILLER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. MzJDFUIWzStvAEtyMAVHx0DHVqUxSjvDFOavcAWMd5DyloTHIDhpvWKy3zVjJpRILzptRSnz zyApIFEvvJVYOFGpOMxWttUMaErMBbHO0aHxVWDxFOE6DvtEt1pqtlJvMRazvM3lVVEGyORp VIO5nRxOyltMlt2FF1OMOnElSHyJyVktOnDxqRV5VdykIKVcqUTqBIHFLVbHMLHlHfSpHPvP IpINFLVI5RE5WCDvtuO3PqHOytG -----END ECHELON KILLER----- C Error #012: printf("Hello world ");
AmigaPhil@ping.be wrote:
I'm now suspecting a mess in the xorg-x11 installation (file missing or such, as were the xorg docs and man pages), so I tried to re-install the xorg-x11 core package (using yast). This too failed (someting related to permission denied).
Is this due because the x-server is already running ? How can I install the xorg-x11-6.8.2-30.i586.rpm from a command line (or prior the x-server is running) ?
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" I'm guessing that "be-latin1" is the one you want. (I was in Belgium only once and didn't know about configuring X then :). There's a few others you could choose from; look in /usr/share/kbd/ keymaps/i386/azerty/ and try a few until you get what you want. Just plug into the xorg.conf (in place of be-latin1) the filename without the ".map.gz" part on the end. You can even "gunzip be-latin1.map.gz", edit it how you want, then "gzip be-latin1.map.gz" back where it came from (though this will probably give someone grand mal seizure). hth.
Thanks.
AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1
-----BEGIN ECHELON KILLER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy.
MzJDFUIWzStvAEtyMAVHx0DHVqUxSjvDFOavcAWMd5DyloTHIDhpvWKy3zVjJpRILzptRSnz zyApIFEvvJVYOFGpOMxWttUMaErMBbHO0aHxVWDxFOE6DvtEt1pqtlJvMRazvM3lVVEGyORp VIO5nRxOyltMlt2FF1OMOnElSHyJyVktOnDxqRV5VdykIKVcqUTqBIHFLVbHMLHlHfSpHPvP IpINFLVI5RE5WCDvtuO3PqHOytG -----END ECHELON KILLER-----
C Error #012: printf("Hello world ");
-- 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
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. 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). 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). So maybe my keyboard problem IS due to a bug in KDE (?), and not to a misconfiguration of xorg as I thought. Still searching... Thanks for your help. AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN ECHELON TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. LWVzcpFxRTaMWAtpWjEUyIBEaJOAtxVkyRD1O3UMzcOvzpKtHF5ExHxtIRzplOtpHzlJvGR5 OhlOYnxyrMbHLDpU0txSSDHMOEalLOVJvtSVBFM5FKAlIvH2II6IdqvOntMVqFlU3vzpFEVt jIyPvVyzIOyVSIWFtO2nHUApyalHDytVIFoGDEzIpMVRVSHfTHT1OMqyqOW1V5BvHCJzzERo RrlJyvdFOFNLqVbRVuqV0uuPGDtGGG -----END ECHELON TEASER----- Do not remove this tag under penalty of law
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-06-15 at 05:51 -0400, ken wrote:
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.
Not Linux, but SuSE, sp 9.3. Some users have reported strange behaviour with the spanish keyboard. It doesn't even happen for all users in the same machine! Me, I can not type acented wovels (áéíóú) in OO, I have to paste them from an xterm. I'll do some tests to refresh my memory. I create a new user. Note: this system was updated from 9.1 KDE (set in spanish): - I can not type accented wovels in konsole. Instead of "áé", I get "'a'e". Letters like "ñ" or "ç" do work. Same problem will happen in other kde applications like kmail or konkeror, but I haven't tried myself today. - xterm works fine. - OO-writer: I can type accented wovels, if started from the application menu, or from konsole or xterm. GNOME (set in English) - Accented wovels work in gnome-terminal, xterm, but not konsole - OOo-writer: no accented wovels reagardless of starting method. GNOME (set in spanish) I don't remember how to change its language... I don't see an entry for it in the gnome control center, except for the keyboard. Ahhh! In keyboard preferences, layout, Spanish was in the "selected layout" list, but the tick box "default" was not ticked. I did, and now OO works. For this user at least... I'll try my default user. Default user (inherited from SuSE 9.1) - ----------- KDE (in spanish) Perfect. GNOME (in english) - Terminals, etc: perfect. - OOo-writer: no accented wovels. keyboard layout: it is diferent. The selected layout is: Spanish [X] Spanish Eliminate dead keys [ ] Spanish Sun dead keys [ ] I remove the "dead keys entries"... no diference. Relogin... no diference. Remove and enter again "spanish"... no diference, still no accents in OO. Ie, no dead keys. :-(
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?
Me too... but you see, I have problems with OO in my normal user in gnome, but not in kde. On the other hand, the problem for a new user in the same system is reversed: kde has problems, gnome doesn't. Weird, isn't it? :-/ - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCsBrctTMYHG2NR9URAtU3AJ9GmaYVM1kzvKiCMSpWNmCTkZRiuwCdEvax uvLEBQmcl668lKEMIzXjPAM= =iIiP -----END PGP SIGNATURE-----
Carlos E. R. (robin1.listas@tiscali.es) wrote something I wish to comment : (news:<Pine.LNX.4.61.0506151308470.11528@nimrodel.valinor> posted on 15-juin-05 13:10:46)
Not Linux, but SuSE, sp 9.3. Some users have reported strange behaviour with the spanish keyboard. It doesn't even happen for all users in the same machine! Me, I can not type acented wovels (áéíóú) in OO, I have to paste them from an xterm.
Check in /var/log/SaX.log Do you see lines like: The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Can't find file "pc" for geometry include ? AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN ECHELON TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. ttWyzvYvapd6EapTp5yJaOHSItkFOOBHltUDpIISjxtFyRFKyEHE0yDctzvHVvySMOxVRxhV OIvLWESOORVtMn53AFJpPG2MlqnR0bWyFIDJHpHnUTArODEz1VApjvADvHVytWOHVCULHVtJ RzzqlctaSGqdEHRBpIbIqotIIKFLzMyUI5FMlzlJlxFO1VVDlOR5MMFqfEvOVMvuVNP3tG== -----END ECHELON TEASER-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-06-15 at 15:33 +0100, AmigaPhil@ping.be wrote:
Not Linux, but SuSE, sp 9.3. Some users have reported strange behaviour with the spanish keyboard. It doesn't even happen for all users in the same machine! Me, I can not type acented wovels (áéíóú) in OO, I have to paste them from an xterm.
Check in /var/log/SaX.log Do you see lines like: The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Can't find file "pc" for geometry include
No, the only errors are related to nvidia. I did run sax once, but my xorg.conf file is derived directly by Yast (I suposse) from the older XF86config. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCsDsztTMYHG2NR9URAuAjAJ9oFfScaHrgPNhIZQWbUljLnOst7gCfeuXZ 9k7z+XP/SEv9G/d9DrDyJzg= =L+S8 -----END PGP SIGNATURE-----
Carlos E. R. (robin1.listas@tiscali.es) wrote something I wish to comment : (news:<Pine.LNX.4.61.0506151626490.16726@nimrodel.valinor> posted on 15-juin-05 15:28:55)
Check in /var/log/SaX.log Do you see lines like: The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Can't find file "pc" for geometry include
No, the only errors are related to nvidia.
I did run sax once, but my xorg.conf file is derived directly by Yast (I suposse) from the older XF86config.
(Or maybe from xorg.conf.saxsave ?) Yes, I've just discovered that the xorg.conf file was modified "by itself" (without running any configuration tool such as Sax2); probably at log in time. Our keyboard problems may have different cause then (?) AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN ECHELON TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. G3MOqRVfVUIFMIVtqxLtM1IlVRMlHTIFMlOnpxMzGaEFBvOdHvO6GzjtDJWUVUyJrSVtnyIh ElOzDacFVTAFLxA5HvObEaVtH2IFpySvJtcvHlOzD3WFpSHtoxSkVRAyIzyBpRjtp0WyYPOC nRptM1IvEaVtEKMHqHqzVR5yHvOdDzIUqFOEpyAlDKSJLIDtp0WyVR55JFOvHlObEvNuPt== -----END ECHELON TEASER----- Your $500,000 is in the mail. (Wait 14 days)
ken (gebser@speakeasy.net) wrote something I wish to comment : (news:<42AFFA2D.5070200@speakeasy.net> posted on 15-juin-05 10:51:41)
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.
xorg.conf was there, already same content as in as xorg.conf-Linux1
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".
It is already.
You might want to check through /etc/sysconfig/language also, to make sure the settings are correct there too.
Not sure. The first entry is a long string which looks like a list of language file. Something like: string(POSIX,ca_ES.ISO-8859-1, ... ,zh_CN.UTF-8) Don't know if it has any importance, but there is nothing related to Belgium. For the French language, there is fr_FR@euro,fr_FR.ISO-8859-1, fr_FR.UTF-8, but there is no fr_BE<something>. Next on the file, the RC_LANG is set to "fr_FR.UTF-8" Other entries which are set to something are: ROOT_USES_LANG="ctype" AUTO_DETECT_UTF8="no" INSTALLED_LANGUAGES="en_GB,en_US,fr_FR"
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.
Good idea ! Hmm, the file is 41Kb, so i'll paste here only the lines that seems relevant to me (and related to the keyboard): (**) Option "CoreKeyboard" (**) Keyboard[0]: Core Keyboard (**) Option "Protocol" "Standard" (**) Keyboard[0]: Protocol: Standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xfree86" (**) Keyboard[0]: XkbRules: "xfree86" (**) Option "XkbModel" "pc105" (**) Keyboard[0]: XkbModel: "pc105" (**) Option "XkbLayout" "be" (**) Keyboard[0]: XkbLayout: "be" (**) Option "CustomKeycodes" "off" (**) Keyboard[0]: CustomKeycodes disabled (**) Option "Protocol" "explorerps/2" (**) Mouse[1]: Device: "/dev/input/mice" (**) Mouse[1]: Protocol: "explorerps/2" (**) Option "CorePointer" (**) Mouse[1]: Core Pointer (**) Option "Device" "/dev/input/mice" (==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50 (==) Mouse[1]: Buttons: 3 (II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap I saw there is also a file SaX.log there. I find it very informative as to the trouble I have encountered while trying to configure the keyboard with SaX2. Here are some lines I find interesting (between "<" and ">" are comments I've added): 13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [ <content of xorg.conf here> ] sh: -c: line 0: unexpected EOF while looking for matching `'' sh: -c: line 1: syntax error: unexpected end of file 13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [ < ... > (**) Option "CoreKeyboard" (**) Keyboard[0]: Core Keyboard (**) Option "Protocol" "Standard" (**) Keyboard[0]: Protocol: Standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xfree86" (**) Keyboard[0]: XkbRules: "xfree86" (**) Option "XkbModel" "pc104" (**) Keyboard[0]: XkbModel: "pc104" (**) Option "XkbLayout" "be" (**) Keyboard[0]: XkbLayout: "be" (**) Option "CustomKeycodes" "off" (**) Keyboard[0]: CustomKeycodes disabled (**) Option "Protocol" "explorerps/2" (**) Mouse[1]: Device: "/dev/input/mice" (**) Mouse[1]: Protocol: "explorerps/2" (**) Option "CorePointer" (**) Mouse[1]: Core Pointer (**) Option "Device" "/dev/input/mice" (==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50 (==) Mouse[1]: Buttons: 3 (II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Can't find file "pc" for geometry include > Exiting > Abandoning geometry file "default" Errors from xkbcomp are not fatal to the X server (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap < ... > The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Can't find file "unknown" for geometry include > Exiting > Abandoning geometry file "default" Errors from xkbcomp are not fatal to the X server < those last 5 lines are reproduced 4 more time > ]
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.
I finally don't think it's a bug in KDE as the keyboard problem also happen when I log in a FVWM session.
Well, I tried to re-install xorg from runlevel 3 using yast in text mode, with the same result (failed).
Why?
I thought I should try the installation without the X server running (and possibly "locking" some files in use (???) )
Well, we still don't have it working for you. So, the next time I'm Belgium you can loan me your non-working car.
:-) AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN ECHELON TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. abpOFtWx1zaptVq5xVytHHyHvIzHrDkEFYEIEHntSlzVFFMpG53FRVzS2OaIqtVMlqRVRDOH UMFScDJpn0vyEBHlIFvtztvJIxUALnOzEGAPFFp3KFTMVFtTOHOMlOtDRyItVHIytdWcElSd aRWSVotICJtVMIx0MvypptjyFlVKUILyDbLRRyzAVMp1pFjqvGvU5vLl1nJ6vOVz6ARHITOO I5JlDJvhfRHBOVvEPnN5WvvOHuhqtt -----END ECHELON TEASER-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-06-15 at 15:12 +0100, AmigaPhil@ping.be wrote:
You might want to check through /etc/sysconfig/language also, to make sure the settings are correct there too.
Not sure.
The first entry is a long string which looks like a list of language file. Something like: string(POSIX,ca_ES.ISO-8859-1, ... ,zh_CN.UTF-8)
It is a comment.
Don't know if it has any importance, but there is nothing related to Belgium. For the French language, there is fr_FR@euro,fr_FR.ISO-8859-1, fr_FR.UTF-8, but there is no fr_BE<something>.
Next on the file, the RC_LANG is set to "fr_FR.UTF-8"
Other entries which are set to something are: ROOT_USES_LANG="ctype" AUTO_DETECT_UTF8="no" INSTALLED_LANGUAGES="en_GB,en_US,fr_FR"
I have: RC_LANG="en_US.UTF-8" ROOT_USES_LANG="ctype" AUTO_DETECT_UTF8="no" INSTALLED_LANGUAGES="en_US,es_ES" But for the keyboard, it would rather be "/etc/sysconfig/keyboard" (text mode): KEYTABLE="es.map.gz" KBD_TTY="tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty20" COMPOSETABLE="clear latin1.add" YAST_KEYBOARD="spanish,pc104" For X, it would be instead configured in "/etc/X11/xorg.conf": Section "InputDevice" Identifier "Keyboard[0]" Driver "kbd" Option "Protocol" "Standard" Option "XkbLayout" "es" Option "XkbModel" "pc102" Option "XkbRules" "xfree86" EndSection Almost the same as you have, considering your log output.
(II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
I only have this error: (EE) Failed to load module "speedo" (module does not exist, 0)
I saw there is also a file SaX.log there. I find it very informative as to the trouble I have encountered while trying to configure the keyboard with SaX2. Here are some lines I find interesting (between "<" and ">" are comments I've added):
The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Can't find file "pc" for geometry include > Exiting > Abandoning geometry file "default"
Then your problem is different from ours... I dunno.
keyboard configuration. Of course, since I don't use that, I can't really make first-hand comments.
I finally don't think it's a bug in KDE as the keyboard problem also happen when I log in a FVWM session.
Possibly. But SuSE is so kde centered, that there are kde things running even when you are not using kde. For example, gnome uses kde help by default! I do know there are some kde bugs in SuSE 9.3 related to the keyboard; I reported my symptoms on another mail in this thread, and they are very similar to what other Spanish people report. But not only in kde, OO is also affected (in gnome?). - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCsD+MtTMYHG2NR9URAgNbAJ4pvBtlg7+rzjQ2LUF6wMAMqzlf4QCdFP6e PWXvNvb4bDfLpdBIyWJfKjA= =U+R3 -----END PGP SIGNATURE-----
Carlos E. R. (robin1.listas@tiscali.es) wrote something I wish to comment : (news:<Pine.LNX.4.61.0506151632500.16726@nimrodel.valinor> posted on 15-juin-05 15:47:36)
I do know there are some kde bugs in SuSE 9.3 related to the keyboard; I reported my symptoms on another mail in this thread, and they are very similar to what other Spanish people report. But not only in kde, OO is also affected (in gnome?).
Just checked with OpenOffice.org. No difference with the keyboard (not worst, not better, same missing keys) AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN DCS 1000 CHEATER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. G3MOqRVfVUIFMIVtqxLtM1IlVRMlHTIFMlOnpxMzGaEFBvOdHvO6GzjtDJWUVUyJrSVtnyIh ElOzDacFVTAFLxA5HvObEaVtH2IFpySvJtcvHlOzD3WFpSHtoxSkVRAyIzyBpRjtp0WyYPOC nRptM1IvEaVtEKMHqHqzVR5yHvOdDzIUqFOEpyAlDKSJLIDtp0WyVR55JFOvHlObEvNuPt== -----END DCS 1000 CHEATER----- WindowsError:018 Unrecoverable error. System destroyed.
AmigaPhil@ping.be wrote:
ken (gebser@speakeasy.net) wrote something I wish to comment : (news:<42AFFA2D.5070200@speakeasy.net> posted on 15-juin-05 10:51:41)
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.
xorg.conf was there, already same content as in as xorg.conf-Linux1
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".
It is already.
You might want to check through /etc/sysconfig/language also, to make sure the settings are correct there too.
Not sure.
The first entry is a long string which looks like a list of language file. Something like: string(POSIX,ca_ES.ISO-8859-1, ... ,zh_CN.UTF-8) Don't know if it has any importance, but there is nothing related to Belgium. For the French language, there is fr_FR@euro,fr_FR.ISO-8859-1, fr_FR.UTF-8, but there is no fr_BE<something>.
Next on the file, the RC_LANG is set to "fr_FR.UTF-8"
Other entries which are set to something are: ROOT_USES_LANG="ctype" AUTO_DETECT_UTF8="no" INSTALLED_LANGUAGES="en_GB,en_US,fr_FR"
These are to make sure that you have the needed character sets, currency symbols, time and date formats, and other stuff like that. I'm not at all familiar with Flemish or whatever language you plan to use, so you're on you own with all that. It won't bear directly on the functioning of the keyboard.
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.
Good idea !
Hmm, the file is 41Kb, so i'll paste here only the lines that seems relevant to me (and related to the keyboard):
(**) Option "CoreKeyboard" (**) Keyboard[0]: Core Keyboard (**) Option "Protocol" "Standard" (**) Keyboard[0]: Protocol: Standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xfree86" (**) Keyboard[0]: XkbRules: "xfree86" (**) Option "XkbModel" "pc105" (**) Keyboard[0]: XkbModel: "pc105" (**) Option "XkbLayout" "be" (**) Keyboard[0]: XkbLayout: "be" (**) Option "CustomKeycodes" "off" (**) Keyboard[0]: CustomKeycodes disabled (**) Option "Protocol" "explorerps/2" (**) Mouse[1]: Device: "/dev/input/mice" (**) Mouse[1]: Protocol: "explorerps/2" (**) Option "CorePointer" (**) Mouse[1]: Core Pointer (**) Option "Device" "/dev/input/mice" (==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50 (==) Mouse[1]: Buttons: 3 (II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
Well, obviously it's not finding the keymap you entered into the xorg.conf file. Go back to my previous email on that topic and make sure the xorg.conf parameter corresponds to an actual file.
I saw there is also a file SaX.log there. I find it very informative as to the trouble I have encountered while trying to configure the keyboard with SaX2. Here are some lines I find interesting (between "<" and ">" are comments I've added):
13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [ <content of xorg.conf here> ] sh: -c: line 0: unexpected EOF while looking for matching `'' sh: -c: line 1: syntax error: unexpected end of file 13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [ < ... > [....]
(**) Option "XkbLayout" "be" (**) Keyboard[0]: XkbLayout: "be"
I thought XkbLayout was supposed to be "be-latin1". So the above explains the error.
[...]
The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Can't find file "pc" for geometry include > Exiting > Abandoning geometry file "default" Errors from xkbcomp are not fatal to the X server (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap < ... > The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Can't find file "unknown" for geometry include > Exiting > Abandoning geometry file "default" Errors from xkbcomp are not fatal to the X server < those last 5 lines are reproduced 4 more time > ]
Comment out whatever lines the above errors are referring to.
[...]
-- 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
ken (gebser@speakeasy.net) wrote something I wish to comment : (news:<42B0427E.1010401@speakeasy.net> posted on 15-juin-05 16:00:14)
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.
Hmm, the file is 41Kb, so i'll paste here only the lines that seems relevant to me (and related to the keyboard):
(**) Option "CoreKeyboard" (**) Keyboard[0]: Core Keyboard (**) Option "Protocol" "Standard" (**) Keyboard[0]: Protocol: Standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xfree86" (**) Keyboard[0]: XkbRules: "xfree86" (**) Option "XkbModel" "pc105" (**) Keyboard[0]: XkbModel: "pc105" (**) Option "XkbLayout" "be" (**) Keyboard[0]: XkbLayout: "be" (**) Option "CustomKeycodes" "off" (**) Keyboard[0]: CustomKeycodes disabled (**) Option "Protocol" "explorerps/2" (**) Mouse[1]: Device: "/dev/input/mice" (**) Mouse[1]: Protocol: "explorerps/2" (**) Option "CorePointer" (**) Mouse[1]: Core Pointer (**) Option "Device" "/dev/input/mice" (==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50 (==) Mouse[1]: Buttons: 3 (II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
Well, obviously it's not finding the keymap you entered into the xorg.conf file. Go back to my previous email on that topic and make sure the xorg.conf parameter corresponds to an actual file.
I saw there is also a file SaX.log there. I find it very informative as to the trouble I have encountered while trying to configure the keyboard with SaX2. Here are some lines I find interesting (between "<" and ">" are comments I've added):
13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [ <content of xorg.conf here> ] sh: -c: line 0: unexpected EOF while looking for matching `'' sh: -c: line 1: syntax error: unexpected end of file 13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [ < ... > [....]
(**) Option "XkbLayout" "be" (**) Keyboard[0]: XkbLayout: "be"
I thought XkbLayout was supposed to be "be-latin1". So the above explains the error.
I tried again to change the Option "XkbLayout" "be" to Option "XkbLayout" "be-latin1" in the files: /etc/X11/xorg.conf /etc/X11/xorg.conf-Linux1 /etc/X11/xorg.conf.saxsave /etc/X11/XF86Config hit CTRL-ALT-BACKSPACE and re-log in ... No improvement. (I restored everything to the initial "be" as to not further mess the X config, and because of the "Please do not edit this file" :-) ) BTW, the "be-latin1" for XkbLayout is linked to the file /usr/share/kbd/keymaps/i386/azerty/be-latin1.map.gz Am I right ? I haven't found a be-latin1 file somewhere else.) AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN DCS-1000 TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. G3MOqRVfVUIFMIVtqxLtM1IlVRMlHTIFMlOnpxMzGaEFBvOdHvO6GzjtDJWUVUyJrSVtnyIh ElOzDacFVTAFLxA5HvObEaVtH2IFpySvJtcvHlOzD3WFpSHtoxSkVRAyIzyBpRjtp0WyYPOC nRptM1IvEaVtEKMHqHqzVR5yHvOdDzIUqFOEpyAlDKSJLIDtp0WyVR55JFOvHlObEvNuPt== -----END DCS-1000 TEASER----- Everything is relative, including this
AmigaPhil@ping.be wrote:
ken (gebser@speakeasy.net) wrote something I wish to comment : (news:<42B0427E.1010401@speakeasy.net> posted on 15-juin-05 16:00:14)
[....]
(I restored everything to the initial "be" as to not further mess the X config, and because of the "Please do not edit this file" :-) )
Post your entire xorg.conf file here. There may be something else wrong with it.
BTW, the "be-latin1" for XkbLayout is linked to the file /usr/share/kbd/keymaps/i386/azerty/be-latin1.map.gz Am I right ? I haven't found a be-latin1 file somewhere else.)
Correct. -- 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
ken wrote:
AmigaPhil@ping.be wrote:
I saw there is also a file SaX.log there. I find it very informative as to the trouble I have encountered while trying to configure the keyboard with SaX2. Here are some lines I find interesting (between "<" and ">" are comments I've added):
13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [ <content of xorg.conf here> ] sh: -c: line 0: unexpected EOF while looking for matching `'' sh: -c: line 1: syntax error: unexpected end of file 13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [ < ... >
It looks like there's a single quote somewhere which is causing the parser some problems. -- 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
ken (gebser@speakeasy.net) wrote something I wish to comment : (news:<42B1569A.8070105@speakeasy.net> posted on 16-juin-05 11:38:18)
I saw there is also a file SaX.log there. I find it very informative as to the trouble I have encountered while trying to configure the keyboard with SaX2. Here are some lines I find interesting (between "<" and ">" are comments I've added):
13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [ <content of xorg.conf here> ] sh: -c: line 0: unexpected EOF while looking for matching `'' sh: -c: line 1: syntax error: unexpected end of file 13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [ < ... >
It looks like there's a single quote somewhere which is causing the parser some problems.
I've just checked in xorg.conf, but haven't found any single quote in there. This error referer to another file/script ? (I'll attach my xorg.conf file in another post.) AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN PRIVATE MESSAGE----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. Tt0VtSLVpKVvSMyFppaIrHyOlFdSDAlvOJ3ycvxpOtc2ytpVUzIyWEanYOHAEyzIHMU6vIIV zHVFGvSIFpna5xBzOatFylxVUDMHAMCyHOTyEKHAjFRVpIqtz5JWthjSEtLFtRJkJVDbMalH zhHqvIOJO1ExR5GBRLtDRt0dOODlVVf1OEqKWqnzvoItqvPEFRlUMFRpdIWPMNlMRHOq5vDO OIbu3tVGt -----END PRIVATE MESSAGE----- That's not a bug! It's supposed to do that!---->*
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-06-16 at 20:20 +0100, AmigaPhil@ping.be wrote:
13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [ <content of xorg.conf here> ] sh: -c: line 0: unexpected EOF while looking for matching `'' sh: -c: line 1: syntax error: unexpected end of file 13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [ < ... >
It looks like there's a single quote somewhere which is causing the parser some problems.
I've just checked in xorg.conf, but haven't found any single quote in there. This error referer to another file/script ?
Yea... to "/tmp/sax2-8841/xorg.conf" - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCsf0ttTMYHG2NR9URAs1IAJ9krIO1jWF1S/nKNe58HOZGYR6/CwCdExMl 9I0XM00DEUk7InXdVMcsZKs= =otiB -----END PGP SIGNATURE-----
Carlos E. R. (robin1.listas@tiscali.es) wrote something I wish to comment : (news:<Pine.LNX.4.61.0506170027160.29459@nimrodel.valinor> posted on 16-juin-05 23:28:58)
13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [ <content of xorg.conf here> ] sh: -c: line 0: unexpected EOF while looking for matching `'' sh: -c: line 1: syntax error: unexpected end of file 13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [ < ... >
It looks like there's a single quote somewhere which is causing the parser some problems.
I've just checked in xorg.conf, but haven't found any single quote in there. This error referer to another file/script ?
Yea... to "/tmp/sax2-8841/xorg.conf"
Isn't it just a copy of /etc/X11/xorg.conf created when calling Sax ? (Anyway, I've checked in this file too, and there isn't any single quote in either.) AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN PRIVATE MESSAGE----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. jtOMBcVYnRy3UHltEjctVvWSpFV6zMoOLSJSzTRCvOEAWaJtIFVtxyynMVUyIhEzPHFKvJbJ ayEqIBt5OyM0qkAz2GAWtHKyVUDt5OppaFIlOAqDOVEvGHpHMpyOHFRlVHIvTRHDplzOySdE R1HzpFWtlUISMHda1zvI5DtDMlIF0LLqxO5DxEFVIvrIRutVfJOpxVnRFvVvbN3qMPlGtO== -----END PRIVATE MESSAGE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2005-06-17 at 01:27 +0100, AmigaPhil@ping.be wrote:
Yea... to "/tmp/sax2-8841/xorg.conf"
Isn't it just a copy of /etc/X11/xorg.conf created when calling Sax ?
I suppose it is the working copy sax makes, modifies, and if successful, finally installs.
(Anyway, I've checked in this file too, and there isn't any single quote in either.)
Ah... :-? Dunno. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCshE/tTMYHG2NR9URApHjAJ4wZ2vBMjBK0/n2gZP431nMQh86wQCZAQ7U yK1qqBR49/52pTe2ZmmVyUk= =8uvV -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-06-15 at 00:02 +0100, AmigaPhil@ping.be wrote:
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 the Spanish list there have been reports of strange keyboard behavior in 9.3 (accentuated vowels may not work), related to kde and OO. You could check if that is your case trying with gnome instead of kde, or viceversa. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCr2wLtTMYHG2NR9URAiycAJ9TVXPnUYGaF/4Txe5kupVsNOoBCACeOc4p QLcKfQHNGnawv+mb8aqwqVo= =LmEj -----END PGP SIGNATURE-----
Carlos E. R. (robin1.listas@tiscali.es) wrote something I wish to comment : (news:<Pine.LNX.4.61.0506150142140.30864@nimrodel.valinor> posted on 15-juin-05 00:45:11)
In the Spanish list there have been reports of strange keyboard behavior in 9.3 (accentuated vowels may not work), related to kde and OO. You could check if that is your case trying with gnome instead of kde, or viceversa.
I don't have Gnome installed (yet) to try, but when I switch back to runlevel 3 (with the "init 3" command from a console), and then test the keyboard on the console, it works fine (at least, I can print the missing e acute and aroba). So is this a KDE bug ??? (I tried a session with FVWM, and the keyboard problem is there too) One step further to the solution (?) Thanks for your help. AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN DCS-1000 TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. W5DvUStGIlVbJyvxBqOVVytytGzVVTaHtORvFxRpl0OaMtHrxcADzHpHdvjDIyxOpELTE5EE FAHz1tYHlnFIFHRyyCpkMKvpvlIqHltASPRoaEEMVpSzWpJILVIVHMOODADqVV3RjOVhFOnz RttfDJByM6FUIOtJHlWMI2VIdaSFMJqOUUvNLpSOy5KMltRnu3czIyFWE5Ovz0bq1PvGFt== -----END DCS-1000 TEASER-----
AmigaPhil (AmigaPhil@ping.be) wrote something I wish to comment : (news:<1013.26T2760T285137AmigaPhil@ping.be> posted on 14-juin-05 00:28:55)
I'm still trying to fix the configuration problem of my keyboard (BE keymap).
I'm now suspecting a mess in the xorg-x11 installation (file missing or such, as were the xorg docs and man pages), so I tried to re-install the xorg-x11 core package (using yast). This too failed (someting related to permission denied).
Well, I tried to re-install xorg from runlevel 3 using yast in text mode, with the same result (failed). Here is the error output: ERROR(InstTarget:E_RpmDB_subprocess_failed) --- /etc/permissions.easy /etc/permissions.local setting /usr/X11R6/bin/Xorg to root:root 4711. (wrong permissions 0711) Finished. moving XF86Config to XF86Config-20050615 2005-06-15 11:06:43 xorg-x11-6.8.2-30.i586.rpm install failed rpm output: error: unpacking of archive failed on file /etc/X11/xkb/compat/accessx: cpio: rename failed - Permission denied Does this help to narrow the possible causes of my keyboard problem ? The keyboard works at runlevel 3, but stop to work properly and cannot be changed as soon as I log in KDE or FVWM. On Usenet, I read that someone else had a problem with a non-working keyboard after a 9.3 installation. But no hint as to a solution, he did recurse to a full re-installation of the 9.3 distribution. (He did not tell if it solved the problem.) AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN PRIVATE MESSAGE----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. pbHJSTKWEEDcIIaVIOEEYRn1darHFvFvDSljVzPWEHFotyOp2WyDtxvHxMzyOyvAAHnlVMOV IRFtylHyhjO3HEJAtSCFpEWHF2AOUcYakEvpBLVDHFWyppAAlJpvIzHzA1qRLqttGSzUtS0t daLMMtDtARzBvEVI5Rt0UJ6qlIOytVVylFTMM5JRIEVIWFOV5nWIOvMMKFvI5JxGpxtOOT5D Fz5L5xVUVtOfOT5INVORObvMlH3uPVtuqEqGt== -----END PRIVATE MESSAGE-----
AmigaPhil@ping.be wrote:
AmigaPhil (AmigaPhil@ping.be) wrote something I wish to comment : (news:<1013.26T2760T285137AmigaPhil@ping.be> posted on 14-juin-05 00:28:55)
I'm still trying to fix the configuration problem of my keyboard (BE keymap).
I'm now suspecting a mess in the xorg-x11 installation (file missing or such, as were the xorg docs and man pages), so I tried to re-install the xorg-x11 core package (using yast). This too failed (someting related to permission denied).
Well, I tried to re-install xorg from runlevel 3 using yast in text mode, with the same result (failed).
Why?
Here is the error output:
ERROR(InstTarget:E_RpmDB_subprocess_failed) --- /etc/permissions.easy /etc/permissions.local setting /usr/X11R6/bin/Xorg to root:root 4711. (wrong permissions 0711) Finished. moving XF86Config to XF86Config-20050615
2005-06-15 11:06:43 xorg-x11-6.8.2-30.i586.rpm install failed rpm output: error: unpacking of archive failed on file /etc/X11/xkb/compat/accessx: cpio: rename failed - Permission denied
Does this help to narrow the possible causes of my keyboard problem ?
No, it makes the problem more complicated.
The keyboard works at runlevel 3, but stop to work properly and cannot be changed as soon as I log in KDE or FVWM. On Usenet, I read that someone else had a problem with a non-working keyboard after a 9.3 installation. But no hint as to a solution, he did recurse to a full re-installation of the 9.3 distribution. (He did not tell if it solved the problem.)
AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1
-----BEGIN PRIVATE MESSAGE----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy.
pbHJSTKWEEDcIIaVIOEEYRn1darHFvFvDSljVzPWEHFotyOp2WyDtxvHxMzyOyvAAHnlVMOV IRFtylHyhjO3HEJAtSCFpEWHF2AOUcYakEvpBLVDHFWyppAAlJpvIzHzA1qRLqttGSzUtS0t daLMMtDtARzBvEVI5Rt0UJ6qlIOytVVylFTMM5JRIEVIWFOV5nWIOvMMKFvI5JxGpxtOOT5D Fz5L5xVUVtOfOT5INVORObvMlH3uPVtuqEqGt== -----END PRIVATE MESSAGE-----
-- 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
participants (3)
-
AmigaPhil＠ping.be -
Carlos E. R. -
ken