I installed DROPLINE, and after I installed it, it worked fine, till I did the DROPLINE Update, now when I reboot, I recieve error @ startup

Error activating XKB configuration.
Probably internal X server problem.

X server version data:
The X.Org Foundation
60700000

If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb

any suggestions on howto fix this problem

I just upgrade from RH9 to FC2 and I get the same error with gnome window manager plus some other problems. I do not get that error when I use KDE manager. I hope someone can shine some light on the fix.

Yeah guys,
mine does the exact same thing. I just upgraded my system from FC 1 to FC 2 and when it came up my smartd (whatever the heck that is) doesn work and i get that creepy xkb config error when i start up.

i have researched it and here´s what ive found:
the xkb is the way X reads the keyboard. supposedly this error is just an improperly configured keyboard. right now i cant type apostrophes. every time i try to type one it just erases the next letter. weird eh? also i have to type in ?´s twice and ~s twice. anybody know how to properly config the keyboard?

best of luck!

i wish i could get this thing fixed

argg

same here..tsk tsk.

i had that - it was really easy to fix. i got it from installing dropline gnome, which uses xorg. i fixed it by using removepkg to remove a certain package, then used the dropline updater to reinstall it, and then it all worked fine.

unfortuntely, i cant remember which one it was.

try making sure that 'grep XkbRules /etc/X11/xorg.conf' returns:
Option "XkbRules" "xorg"
if not, change it, then the same for /etc/X11/XF86Config.
then run setxkbmap -rules xorg -layout us (or gb or whatever)

ill try and find out the name of the package for u

got it. run:
grep xkb/rules /var/log/packages/*
you will get something like this:
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/xorg.lst
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/sun.lst
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/sun
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/xorg.xml
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/xorg
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/README
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/sgi
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/xorg-it.lst
/var/log/packages/xorg-6.7.0-i686-#dl:etc/X11/xkb/rules/sgi.lst

where # is a number. mine is currently 3. then leave gnome and run as root:
removepkg xorg-6.7.0-i686-#dl.tgz

replacing # with the number. then i ran the dropline installer to get it back.
this will of course be different for red hat, as it uses rpm, but im sure you can adapt it pretty easily. maybe something like rpm -(whatever to remove) xorg-6.7.0-i686-#dl.rpm ?
instead of the dropline installer, you could try running rpm -(to install) xorg-6.7.0-i686-1dl.rpm .

i hope this helps

a simpler method is presented in bug #120858 in the bugzilla for Fedora ...

----
Additional Comment #16 From Ralf Ertzinger on 2004-04-17 08:02 -------

I solved this by simply adding a symlink in /usr/X11R6/lib/X11/xkb/rules:

ln -s xorg.lst xfree86.lst

Temporary, sure, but setxkbmap is happy again.
----

This worked like a charm for me and hopefully future updates of xorg will fix things in the background ... but having this symlink should not harm anything.

Bob,

I just wanted to say a great big thank you!

I have had the same problem since upgrading and it had been bugging me to death. Such a simple fix. Even though the problem was only a minor inconvenience (requiring one mouse click) it somehow spoilt things beyond all proportion.

Thanks again...

Mark

I too want to thank Bob, nice and simple fix. Just what the doctor ordered.

Stew

Okay,
Bob, Your symlink worked perfectly. Thank you.

I had no tangible system problems anyway. No real keyboard errors that I could find. I just had that error message at login. still. It was irritating.
I am pleased with the simplicity of the solution. I am still wondering why it happened on one system and not another.
I loaded ferdora 2 fresh and new on one system and I upgraded another system. The upgrade was the one with the error message problem. go figure.
but as I said, your solution worked completely. Kudos to you.
Islander.

I have had this problem on numerous distros with xorg. Finally a fix maybe, although I have not tried it yet.

To be blunt, xorg is getting on my last nerve and the developers need to get off their fat asses and do it right if they even halfway expect xorg to supercede xfree. It's just been one blooper after another with xorg. Xcomp, translucency, etc turned out to be a bust unless your on a high end machine that can handle the cpu power for it and that's if it doesn't crash before you even get to try it out. Then the problems with keyboard functions, switching vt's etc.

Hey XORG what is it, are you blatently screwing up releases for users of US keyboards. I know a bit far fetched but with all this Xborg madness who can really tell what the heak is going on.

*sighs* Linux........................one problem after another. Thats's what keeps me goin. ;-)

I did this, but when I restart X, metacity seems to hang. I am able to login as root and not get the error message. I am not sure how to fix this for the user.

I ran into this error after reconfiguring my keyboard layout using I managed to solve it by running