SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Here's the keyboard section for my xorg.conf file. I might be wrong, but this problem sounds like this section on your computer needs to be tweaked. The stuff below works well for a Microsoft Natural keyboard.
Code:
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "microsoft"
Option "XkbLayout" "us"
EndSection
It seems to me like the solution lies with xkeyboardmap. Since most configuration tools are basically glorified frontends for BASH, sed and AWK, I suspect that all xkeyboardmap is doing is writing to a configuration file somewhere that's being overwritten everytime you log out or in. Assuming that's the case, all you need to do is figure out what file(s) that program is editing and write a script that will put things back to the way you want them when you log in again. It's also pretty likely that if the configuration file's being overwritten a lot that there's a note in that file saying what script is doing it. Also, you could try some of the other keyboard tools in Gnome. (I'd be more specific but my internet connection is on the fritz in Linux so I'm currently booted into Windows XP.)
If you can't figure it out using some more conventional methods, you can try this:
1) Load up Gnome and WITHOUT running xkeyboardmap and type into a console:
Code:
cd /
su -c "ls -lR > /tmp/sysdir.txt"
<type your root password>
2) Run xkeyboardmap and set everything to how you like it. Play with the buttons a bit to make sure that they work. Now type:
Code:
cd /
su -c "ls -lR > /tmp/newsysdir.txt"
<type your root password>
diff /tmp/sysdir.txt /tmp/newsysdir.txt
3) Compare the "diff" results. Anything with a "<" at the beginning of the line is a line from your system directory before you ran xkeyboardmap. Anything with a ">" at the beginning of the line is a line from your system directory after you ran xkeyboardmap. Look for differences in filesizes and/or any new files that were created presumably by xkeyboardmap. Check the files for things relating to your keyboard and chances are you'll find a winner! You can delete the files you just created in /tmp when you're done with them.
Sorry I couldn't be of more help (hopefully I'll get my modem working right in Linux soon...). Good luck!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.