"Error activating XKB configuration." - Requires manual xorg.conf editing

after searching the forums, I modified the xorg.conf and hashed the line:
# Option "XkbVariant" "qwerty"

It helped, everything seems to be ok.

I installed Feisty. On Dapper I had a qwerty Polish keyboard, a common standard in Poland. In Feisty I do not have the same Polish keyboard - it is qwertz instead with Polish diacritics in different places.

Unlike the user above there was no "XkbVariant" line in my xorg.conf file.

Instead, in the line
 Option "XkbLayout" "ie"

I changed ie to pl.
Now I have the Polish qwerty keyboard I need - however I get a warning message when gnome starts.

It is a bug if a feature once available easily on Preferences > keyboard can now be only achieved by various editing of xorg.conf

On reading the Polish forums forum.ubuntu.pl there is a sticky explaining how to edit the xorg.conf file as above to get Polish keyboard.

One poster:
"I can have a keyboard in any language I want except Polish"

Another:
"Polish letters worked fine in Dapper but in later versions I not not have all the characters in the usual places"

These seem to refer to Edgy, but the problem is also in Feisty

thanks,
I am with Feisty right now, installed as beta and then upgraded. No
issues with keyboard whatsoever.
regards
radek

On 4/30/07, Bloch <email address hidden> wrote:
> On reading the Polish forums forum.ubuntu.pl there is a sticky
> explaining how to edit the xorg.conf file as above to get Polish
> keyboard.
>
> One poster:
> "I can have a keyboard in any language I want except Polish"
>
> Another:
> "Polish letters worked fine in Dapper but in later versions I not not have all the characters in the usual places"
>
> These seem to refer to Edgy, but the problem is also in Feisty
>
> --
> Lack of Polish diacritic symbols during writting, no Polish keyboard activated
> https://bugs.launchpad.net/bugs/67188
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Pozdrawiam

Radek

I see above that some found a solution to this bug by commenting out the line in the xorg.conf. This, from what I understand, is the reverse of the correct solution.

If you look in gconf-editor : /desktop/gnome/peripherals/keyboard/kbd/overrideSettings you'll see that these settings are now considered deprecated and should not be used. xorg.conf settings *should* be used. In my testing clearing all values in the above gconf-editor key and placing the proper value in xorg.conf also result in removing the errors reported above.

I suppose this raises another bug. Is System > Preferences > Keyboard now making changes to key values that are deprecated where it should be changing values in xorg? Perhaps we need something more similar to RHEL/FC 'system-config-keyboard'?

Christer, thanks for the research into this. Yes, it does sort of sound like maybe gnome-keyboard-properties is doing something improper. I've added control-center to this bug. If someone can confirm that it's being done by that tool, then it can be handled there.

I can confirm that Christers above suggested solution of clearing all values
via the gconf-editor and placing the correct values in xorg.conf manually
has worked to solve this problem in BOTH the instances where we had this
problem with the Swedish keyboards.

Christer, thanks for the research into this. Yes, it does sort of sound
> like maybe gnome-keyboard-properties is doing something improper. I've
> added control-center to this bug. If someone can confirm that it's
> being done by that tool, then it can be handled there.
>
> ** Also affects: control-center (Ubuntu)
> Importance: Undecided
> Status: Unconfirmed
>
> --
> "Error activating XKB configuration." - Requires manual xorg.conf editing
> https://bugs.launchpad.net/bugs/67188
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Andreas Rönnqvist
<email address hidden>
<><><><><><><><><><>
www.dreamscarredpress.com
www.omegaproject.se

Do you have easy steps to trigger the bug? What gconf values did you change?

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

A variant of this bug is present in Gutsy Gibbon / Tribe 5 / Macbook / Finnish keyboard layout.

After changing the keyboard configuration (installer didn't get it right), I get a Gnome warning message during the boot.

Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10300000

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/kbd

moo@valko:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [fi mac]
 model = macbook78
 options = [lv3 lv3:ralt_switch,lv3 lv3:alt_switch,grp grp:alts_toggle]
 overrideSettings = true

moo@valko:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "se", "", "lv3:ralt_switch"
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "se", "", "lv3:ralt_switch"
moo@valko:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd

I pinpointed my problem:

If you use layout Finland/Macintosh instead of Finland/Generic, you'll get this error message every time Gnome tries to set keyboard properties.

Selecting finland, macintosh doesn't create the issue on gutsy, could you try if that's still happening to you on it?

same here, I'm getting the same issue at my end.

Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10300000

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/kbd

shirish@Mugglewille:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "", ""

shirish@Mugglewille:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us,in bolnagri]
 model =
 options = [grp grp:alts_toggle]
 overrideSettings = true

Now just to make sure that xkeyboard-config is present I just did :-

shirish@Mugglewille:~$ dpkg -l xkeyboard-config
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
un xkeyboard-conf <none> (no description available)

which shows that xkeyboard-conf is uninstalled

doing a search shows me this :-

shirish@Mugglewille:~$ aptitude search xkeyboard
p xkeyboard-config - Transitional package for xkb-data

then did a search for xkb-data

shirish@Mugglewille:~$ aptitude search xkb-data
i xkb-data - X Keyboard Extension (XKB) configuration d
p xkb-data-legacy - Classic XKB data

xkb-data is installed & it is 0.9-4ubuntu2 , so I hope the correct things are there. Any help would be appreciated.

looking at /etc/X11/xorg.conf this is what it looks like :-

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "us"
EndSection

From the forums did the Driver from "kbd" to "keyboard" let's see if that workaround works or not.

Same problem reported with Rev. A 1998 iMac in Gutsy (these problems did not occur in Feisty):

_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "mac", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "mac", ""

 layouts = []
 model = macintosh
 overrideSettings = true
 options = []

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "us"
 Option "XxbVariant" "mac"
EndSection

I can confirm this after updating to newest xkb-data.

gnome-keyboard-properties also spit out...

dpy: 0x80776b8
evt/error/major/minor: 94/163/1/0

changing Driver from "kbd" to "keyboard" didn't solve the problem as the workaround mentioned above also didn't solve it, unfortunately :(

Same here with a "brazilian portuguese" keyboard with "abnt2" variant.

marcos@autoxtreme:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "abnt2", "br", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "abnt2", "br", "", "grp:alts_toggle"
marcos@autoxtreme:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [br]
 model = abnt2
 options = [grp grp:alts_toggle]
 overrideSettings = true
marcos@autoxtreme:~$

And here the xorg.conf configuration for the keyboard:
Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "abnt2"
 Option "XkbLayout" "br"
EndSection

Same here using gutsy with all updates

rafael@rafael-laptop:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us-intl", "intl", "lv3:ralt_switch"
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us-intl", "intl", "lv3:ralt_switch"

rafael@rafael-laptop:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 model =
 options = [lv3 lv3:ralt_switch,altwin altwin:super_win]
 overrideSettings = true

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "us-intl"
 Option "XkbVariant" "intl"
 Option "XkbOptions" "lv3:ralt_switch"
EndSection

I can confirm that reverting to feisty's version of the package works fine and fixes the problem.

Editing xorg.conf and changing driver from "kbd" to "keyboard" solved my own XKB error after using 'system - preferences - keyboard' in Feisty. This error occurred when I reset keyboard layout to default settings after getting confused exploring different keyboard layouts. I have a generic uk keyboard. I not an expert. I think this is part of the same issue - i.e. ubuntu's gui keyboard configuration tool generating an xkb error? Happy to generate a new bug report and/or further details if required.

Can confirm this bug!

Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10300000

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/kbd

pgd@pgd-laptop:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "no", "no", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "no", "no", ""

pgd@pgd-laptop:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 model = pc101
 overrideSettings = true
 options = []
pgd@pgd-laptop:~$

I tried every solution given in the entire internet for the bug -- none worked. Until I edited xorg.conf directly to reflect the real situation I had:
Section "InputDevice"
        Identifier "Generic Keyboard"
        Driver "kbd"
        Option "CoreKeyboard"
        Option "XkbRules" "xorg"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "us_intl"
EndSection

No idea why...

jlinkels

This bug seems to still affect people quite regularly. There were several additional reports that I've marked as duplicates in hopes of consolidating the information.

My sv keymap does not work after hardy restart.

Fel vid aktivering av XKB-konfiguration.
Det kan ske under diverse omständigheter:
- ett fel i biblioteket libxklavier
- ett fel i X-servern (verktygen xkbcomp, xmodmap)
- X-server med inkompatibel implementation av libxkbfile

Versionsdata för X-servern:
The X.Org Foundation
10400090

Om du rapporterar detta som ett fel ber vi dig ta med:
- Resultatet av xprop -root | grep XKB
- Resultatet av gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd

xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "sv", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "sv", "", ""

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = [sv,fi]
model =
options = [grp grp:alts_toggle]
overrideSettings = true

I use "kcmshell keyboard_layout" to remove active layout and adding it again to the layouts.
This is a workaround for me.

             the daily software update yesterday fixed this bug
             there are many bugs open with this default keyboard problem, so the correct package seems
             to be "gnome-settings-daemon"
             Have a look at Bug #188171
             This bug was fixed in the package gnome-settings-daemon - 2.21.90.2-0ubuntu2

                    * debian/patches/80_from_upstream_fix_xkb_loading.patch:
                       - change from upstream, fix xkb loading (lp: #188171)

Hello,
I changed the setting in System, Settings, keyboard by adding Finland to the selection. Special characters does work for the new setting but are lost after system reboot. They have to bee selected again.

Here is my output for "xprop -root | grep XKB" after changing settings and reboot.
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "sv", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "fi", "", "grp:alts_toggle"

and here is the output for "gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd"
 layouts = [fi]
 model =
 options = [grp grp:alts_toggle]
 overrideSettings = true

Adding a screenshot as attachement where new layout is working before reboot.

I confirm this too. After system rebooting I have to go on System>Keyboard>Layout disposition and click on Apple Laptop to have accentuation working again for brazilian characteres.
mabovo@macbook:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "macintosh(macbook79)", "pt", "mac", ""
_XKB_RULES_NAMES(STRING) = "xorg", "apple_laptop", "us", "basic", "grp_led:scrol l,compose:rwin,lv3:lwin_switch"
mabovo@macbook:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us basic]
 model = apple_laptop
 options = [grp_led grp_led:scrol l,Compose key compose:rwin,lv3 lv3:lwin_switch]
 overrideSettings = true

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "macintosh(macbook79)"
 Option "XkbLayout" "pt"
 Option "XkbVariant" "mac"
# Option "XkbOptions" "lv3:ralt_switch,grp:alts_toggle,grp_led:scrol l"
EndSection

[ 25.821317] input: Apple Computer Apple Internal Keyboard / Trackpad as /devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/input/input1
[ 25.829802] input,hidraw0: USB HID v1.11 Keyboard [Apple Computer Apple Internal Keyboard / Trackpad] on usb-0000:00:1d.0-2
[ 25.833010] input: Apple Computer Apple Internal Keyboard / Trackpad as /devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.2/input/input2
[ 25.841775] input,hidraw1: USB HID v1.11 Device [Apple Computer Apple Internal Keyboard / Trackpad] on usb-0000:00:1d.0-2
[ 25.847261] hiddev96hidraw2: USB HID v1.11 Device [Apple Computer, Inc. IR Receiver] on usb-0000:00:1d.2-2
[ 25.864396] input: HID 05ac:1000 as /devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/input/input3
[ 25.873717] input,hidraw3: USB HID v1.11 Keyboard [HID 05ac:1000] on usb-0000:00:1d.3-1
[ 25.888216] input: HID 05ac:1000 as /devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.1/input/input4

Finally I found the perfect match for MacBook 2nd gen UK keyboard configured for brazilian portuguese characters:
mabovo@macbook:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "apple_laptop", "us", "basic", "grp_led:scrol l,compose:rwin,lv3:lwin_switch,grp:alts_toggle"
_XKB_RULES_NAMES(STRING) = "xorg", "apple_laptop", "us", "basic", "grp_led:scrol l,compose:rwin,lv3:lwin_switch,grp:alts_toggle"

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "apple_laptop"
# Option "XkbModel" "macintosh(macbook79)"
 Option "XkbLayout" "us"
# Option "XkbLayout" "pt"
 Option "XkbVariant" "basic"
# Option "XkbVariant" "apple_laptop"
# Option "XkbVariant" "mac"
 Option "XkbOptions" "grp_led:scrol l,compose:rwin,lv3:lwin_switch,grp:alts_toggle"
EndSection

Happened to me after last Hardy Alpha kernel update.

$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us,ru", "winkeys", "grp:alt_shift_toggle,grp_led:scroll"
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us,ru", "winkeys", "grp:alt_shift_toggle,grp_led:scroll"

$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 model = sven
 options = [grp_led grp_led:caps,grp grp:caps_toggle]
 overrideSettings = true

# from /etc/X11/xorg.conf
Section "InputDevice"
        Identifier "Generic Keyboard"
        Driver "kbd"
        Option "XkbRules" "xorg"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "us,ru"
        Option "XkbVariant" "winkeys"
        Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
EndSection

What can be wrong with this config?

Same problem here after yesterday's hardy update.
Very, very, very, very, very, very annoying.

Outpput of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd

layouts = []
 model =
 overrideSettings = true
 options = []

Output of _xprop -root | grep XKB

_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "de_CH", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "de_CH", "", ""

Will try to edit xorg.conf manually. Let's hope it works, damn it.

Manually editing /etc/X11/xorg.conf and replacing "Driver "kbd"" with "Driver "Keyboard"" worked for me. After rebooting the keyboard layout was "USA", but adding "Switzerland" and removing "USA" was no problem. Here the section of my xorg.conf:

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "Keyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "de_CH"
EndSection

Possible duplicates or related bugs:
Bug #210734
Bug #207812
Bug #209493
Bug #210893
Bug #215699
Bug #217568
Bug #210140
Bug #120420

I've upgraded Ubuntu 7,10 to 8.04, and when I tried add polish keyboard, then i saw

Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10400090

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/kbd

it always shows when i run system.

tomek@tomek-laptop:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "pl", "pl", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "pl", "pl", ""

tomek@tomek-laptop:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = [pl pl]
model =
options = [grp grp:alts_toggle]
overrideSettings = true

I installed Hardy on a clean harddisk. This fixed the keyboard problems for me.

Fresh install of Hardy Heron on a MacBook Pro (Gen. 3), this problem still persists when trying to select the MacBook/MacBook Pro option from System => Preferences => Keyboard.

I was able to fix this problem by changing the xorg.conf line:

Option "XkbVariant" "asdf!@?"

to

Option "XkbVariant" "basic"

Then the error no longer appeared when loading gnome.

Confirmed for Intrepid Alpha (64-Bit) as of today. This error occured since an update yesterday. (Originally a fresh install of Intrepid Alpha 2 with permanent updates.) MacBook Pro rev. 3.

----
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10499906

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/kbd
----

There are various MacBook Pro keyboard issues in launchpad. I don't know if this a keyboard issue. Since this error message occurs, something is wrong with the theme, too: E.g. Firefox has a blue window bar instead of a brown one and a slightly different look, too.

xprop -root | grep XKB says

----
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "de", "mac_nodeadkeys", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "de", "mac_nodeadkeys", ""
----
.

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd says

----
layouts = [de mac]
model = macbook79
options = [grp grp:alts_toggle]
----

Please mind that there are several other MacBook Pro keyboard issues which have already been reported.

Same problem here on Hardy:
xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "de_ch", "de_ch", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "de_ch", "de_ch", ""

 gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [de_ch de_ch,ch de_nodeadkeys]
 model =
 overrideSettings = false
 options = [grp grp:alts_toggle]

Problem remains after newest available updates.

Hi,

For me , it seems that removing the line
      Option "XkbVariant" "basic"
from xorg.conf
and reconfiguring the keyboard in gnome solved the problem.
(I think it has been an upgrade problem from Gutsy to Hardy

This is not only an upgrade problem. It also occured on a fresh install (originally Alpha 1 or 2, problem occured about 10 days ago and remains).

Yeah, and the xorg.cong trick didn't solve the problem.

Now, i've added this command to my X startup programs:
setxkbmap ch
to set my keyboard correctly, this works.

Apparently, currently on Intel MacBook Pros not only the keyboard is not being detected but it is also completely wrong. Try System -> Einstellungen -> Tastatur, choose "MacBook/MacBook Pro (Intl)" + "Germany Macintosh" and choose "Print Layout Diagram". I get a DESKTOP KEYBOARD DIAGRAM! Now I stop wondering why there is so much wrong with Ubuntu and this keyboard! You can look at this diagram in https://bugs.launchpad.net/xkeyboard-config/+bug/261573, it's called This_is_what_Ubuntu_thinks_to_be_a_MacBook_or_MacBook_Pro_keyboard_Intel_Germany_Macintosh.pdf.

Can anyone tell the developer about this? Seems to me he doesn't really read what we are discussing here.

Once more, here is what the keyboard really looks like: http://www.praezisionoptoelektronik.de/upload/Tastatur/Apple15/Apple15b.jpg.

Ubuntu 8.04, german version.
Thoug german keyboard defined, no german umlaute available. Also sharp s, "at" inside of email-adresses and so on don't work.
System > Settings > Keyboard > "Belegungen" (2nd Tab) > Tastaturmodell : Changing this value from previously 101 generic pc to 105 generic pc und clicking onto OK displays err-msg:

=================
Error activating XKB configuration.

It can happen under various circumstances:

- a bug in libxklavier library

- a bug in X server (xkbcomp, xmodmap utilities)

- X server with incompatible libxkbfile implementation

X server version data:

The X.Org Foundation

10400090

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/kbd
=================
Here are the results:
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "de", "pc105", "lv3:ralt_switch"

_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "de", "pc105", "lv3:ralt_switch"

The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd

layouts = []

 model = btc5126t

 overrideSettings = true

 options = []

Gruss, Gerhard

uffff same shit happened to me... so fustrating... but I find a solution to me. I don't know if it will work to anyone else...

Situation: I got an XCB error message each time I restart the system and i don't have a correct keyboard localization ( the especial characters doesn't work )

I fixed that by clicking in System->Preferences->keyboard->Recover Factory defaults ( or watherer is called.. I'm spanish user and for me it's call "Restablecer valores predeterminados").
Now I only have 1 keyboard distribution: España ( in my case ) and the keyboard model is Generic PC 105k (intl)
Then I reboot the system. At this time, I don't get the ugly message error.... but especial characters like # or ¬ doesn't work yet.
To fix that I edited /etc/X11/xorg.conf file and I commented the XkbVariant Option to have only one existing layout...
It looks like this:
Section "InputDevice"
        Identifier "Generic Keyboard"
        Driver "keyboard"
        Option "CoreKeyboard"
        Option "XkbRules" "xorg"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "es"
        #Option "XkbVariant" "ca"
EndSection

Now when reboot the system I have no error and I got the correct keymapping for my language (spanish).
This steps solved my problem... hope it helps somebody ; )

.... Sorry for my english level : \ ....
Eric Garcia

Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10502000

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/kbd

xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us", "nodeadkeys", "grp:alt_shift_toggle,grp_led:scroll"
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "nodeadkeys", "grp:alt_shift_toggle,grp_led:scroll"

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us nodeadkeys,ru]
 model =
 options = []

part of xorg.conf:
Section "InputDevice"
        Identifier "Generic Keyboard"
        Driver "kbd"
        Option "CoreKeyboard"
        Option "XkbRules" "xorg"
        Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
        Option "XkbLayout" "us,ru(winkeys)"
        Option "XkbVariant" "nodeadkeys"
        Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
EndSection

Keyboard Layouts not working after update to Intrepid.

Is anyone going to hand over this information to the developers?

Btw. I think this is related with https://bugs.launchpad.net/xkeyboard-config/+bug/261573.

This bug appears to me on intrepid (ubuntu 8.10)

root@Acer:~# xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "es", "latin9", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "es", "latin9", ""

root@Acer:~# gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 options = []
 model =
 layouts = []

I've change with all the different value my Xorg.conf and reboot about 100 times. but nothing happens....

The last one is:

Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "Keyboard"
    #Driver "kdb"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "es"
EndSection

UNTIL I've found the command:

setxkbmap es

The command setxkbmap works for me but I've an error at each startup of gnome.

This bug is very, very widespread so bumping up the priority another notch.

This bug continues to persist.

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

are errors from /var/log/messages related to the problem. There are 30 duplicates of this bug.

I had the same problem and just solved it.

# # # MY COMPUTER # # #
Panasonic Let'sNote (ToughBook) W4

# # # PROBLEM # # #

After upgrading from Ubuntu 7.10 Gutsy to 8.04 Hardy, the dialog described in the first post was shown when I log in the Ubuntu system.

As a result, I could not configure the keyboard setting (e.g. swap [Ctrl] & [Caps Lock].)

# # # HOW DID I SOLVED IT # # #

As some of them mentioned, first I modified xorg.conf, then reset the keyboard setting.

1 Open xorg.conf
sudo gedit ../../etc/X11/xorg.conf

2 Scratch the line:
# Option "XkbVariant" "106,"

3 Save & close it.

4 [System] -> [Keyboard] -> Tab [Layout]

5 Click [Reset] and apply the default style.

6 Restart the Ubuntu system.

On Jaunty (Alpha 3) AMD64, I had the same issue:
On login, an alert box saying "Error activating XKB configuration".
When I went to Preferences > Keyboards > Layouts, I found that I had no Layouts to choose from.

Fixed it with: sudo apt-get install --reinstall xkb-data

I'm using Jaunty (Alpha 3) i386 just now and still have this issue.
I've tried reinstalling xkb-data as jeswin suggested above, but still getting the error on startup.

06 Febrary 2009 12:44:19 (ITALY)

I updated Kernel to last version and other libraries and now not work keypad and lights which stay up on keypad.

Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10502000

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/kbd

xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "es", "", "lv3:ralt_switch"
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "es", "", "lv3:ralt_switch"

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 model =
 options = [lv3 lv3:ralt_switch,keypad keypad:comma]

Thank you for your help :)
Kind Regards
Vincenzo

Excuse me but not add an important information.

I have a spanish keyboard ;)

macbook1,1
Preferences Keyboard Layout set to macbook/macbookpro. have two layouts (german and US) activated.
the above mentioned error occurs at every login.

The X.Org Foundation 10502000

xprop:
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us", "mac", "lv3:ralt_switch"
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,de", "mac,mac", "lv3:ralt_switch,grp:alts_toggle"

gconftool-2:
 layouts = [us mac,de mac]
 model = macbook78
 options = [lv3 lv3:ralt_switch,grp grp:alts_toggle]

(options speeks of right alt here, there is no right alt on a macbook. problem?)

up to date intrepid 64bit
_XKB_RULES_NAMES_BACKUP(STRING) = "base", "pc101", "us", "", "

 layouts = []
 model =
 options = []

horribly annozying

fixed it for me
turned out my /usr/share/X11/xkb/rules directory was empty

had to reinstall xkb-data

maybe a bug in ext3? as the last shutdown was 100% for sure a clean one

I have the feeling that this bug here might be a collection of several distinct issues, which all look the same due to lack of precise error messages. I filed bug #328980 asking for error messages to be displayed to the user.

Until then, you might use the attached script to learn more about this kind of error. Download it, and then call "sudo bash DownloadedScriptName install" in order to install a wrapper around xkbcomp. Then reproduce the issue, and have a look at /tmp/xkb.*/* for more details about xkbcomp invocations, especially /tmp/xkb.*/err for standard error messages. Once you are done, you can invoke the script with "sudo bash DownloadedScriptName uninstall" to remove the wrapper and "sudo bash DownloadedScriptName clean" to delete the collected data.

With such a wrapper, you can get additional information, like shown in bug #327963 for my own Mac-related issue. Maybe with this information it becomes possible to distinguish the different causes of xkb error messages, and address them appropriately.

What I'd recommend is building libxklavier and trying tests/test_config app - trying to set the required configuration.

Bryce, can you take a look at this, please?

pitti, I think gagern made a good point in comment #61 that this is an aggregation of issues that are difficult to investigate due to lack of specific error messages, due to bug #328980 - gnome redirects error messages to /dev/null.

I think this is an important issue, but there are work arounds to the issues being encountered, and the dupes are really a series of other bugs that result in the same message.

Sergey hinted to rebuild libxklaver and try test_config, could somebody having the issue do that?

I am just testing with Ubuntu 9.04 Alpha 5+ with all of today's updates. Chose "Apple MacBook/MacBook Pro (Intl)". Getting the usual XKB error. The only difference towards Ubuntu 8.10 is that now neither the CapsLock light nor the CD/DVD eject button work any more, filing separate bugs for this.

Starting with Jaunty, people seeing this "Error activating XKB configuration" dialog might have a look at the .xsession-errors file in their home directory. Error messages from xkbcomp will end up there, and others might as well. Maybe the information from these files can be used to differentiate the huge number of bugs duped here, and identify the actual causes.

same in jaunty:
xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "ch", "de_mac", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "ch", "de_mac", ""

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 options = [altwin altwin:super_win]
 model = macbook79

.xsession-errors;
...
(gnome-panel:17719): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE
Error: No Symbols named "de_mac" in the include file "macintosh_vndr/ch"
                  Exiting
                  Abandoning symbols file "(null)"

** (gnome-settings-daemon:17694): WARNING **: Could not activate the XKB configuration
....
hth

h

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

raketenman wrote:
> Error: No Symbols named "de_mac" in the include file "macintosh_vndr/ch"

Same as my bug #327963, I guess.

You can either have a Macintosh Swiss keyboard model with a German
layout, or you can have a generic keyboard model with a special
Macintosh German layout. As the former uses the keys as labeled out on
the Mac, it's probably what you want. So simply change the layout from
de_mac to de, and you should be all right.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpohM8ACgkQRhp6o4m9dFvvcQCfW9YR48QkH5Fevy9Gz7pP7OOJ
cEoAnjLmPOolFNB2fDJLg1pXtMBb8tPZ
=x4FP
-----END PGP SIGNATURE-----

jep that's it - changed keyboard model to generic 102 & layout to Switzerland German (Macintosh) worked for me!
thanks

I'm confused. It seems to be that that solution is to set the keyboard to Generic and not have the proper settings.. That can't be right. Can it!?

spbrereton, if what you experience is in fact bug #327963, then I believe that you should set the MODEL to something mac (e.g. "macintosh_vndr/ch") and the LAYOUT to a variant not mentioning mac (e.g. "de", not "de_mac").

The reason is that the layout files for mac models simply don't mention any specific mac layout variants, as all the mac model layouts are for mac. In other words, the "macintosh_vndr/ch" file describes a layout called "de" which fits the default swiss mac layout, but no layout called "de_mac". Bug #327963 has been turned into a request to introduce the latter as an alias to the former, in order to avoid this confusion. If you want to support that, subscribe to that bug and/or mark it as affecting you as well.

The other way, using a generic MODEL with a *_mac LAYOUT does work as well, as far as the configuration files are concerned. The result is probably not optimal, though, as that configuration is intended to simulate mac-like behaviour on a non-mac keyboard. So if your keyboard was built by apple, the other approach is preferable.

Further discussion on the speific issue of mac keyboard models with mac layout variants should probably go to bug 327963 as well, as that bug is more specific, while this one here does deal with several other and probably unrelated issues as well.

Thanks for the feedback. Perhaps I am in the wrong bug - but 327963 doesn't seem to be right for me either.

In effect, I have no need for any variant of the Mac keyboard. I have a MacBook Pro 2.2 (now running Karmic, though the problem was also in Jaunty). I installed VirtualBox 3.0 to run XP and everything was working prefectly (i.e. in XP, to get to the Alt-F4 key, I would still have to use the Mac configuration of ALT+FN+F4). I was happy.

Then for some reason I lost the Keyboard in the Host (although a plugged USB KB works). At the same time, the keyboard in XP went to a generic 105 - meaning the that I can't now access the FN key to get to Home/End/F-keys, etc. To correct, this I attempted to specify to Ubuntu that I had a Mac Keyboard with US layout. This was where I ran into this bug. The only way I could fix it was to go back to a Generic 102 (or 105) keyboard.

Ubuntu still interprets the key-presses correctly. But something isn't passing it through to the Guest OS properly (meaning I have no delete, only backspace in XP :) Should I in fact be in 327963?

So let me get this right: you're now working with a USB keyboard plugged into your MacBook Pro?
Is it a Mac keyboard, or some other, more PCish keybord? If the latter, then "Generic" is most definitely the way to go, I'd say.
When you claim that a Generic 102 keyboard was the "only way", have you tried configuring a Mac model with a simple (i.e. not mentioning mac) US layout, as I suggested?

I know little about VirtualBox, but I assume that it the ransfer of key events from the host OS to the guest OS works on the level of scan codes, not characters. I don't know whether these scan codes are passed dirctly as received, or rather generated according to some kind of virtual keyboard the guest sees. In any case, I assume that keyboard layout configured in the host should have little to do with this. Instead, twaking configuration options in the guest OS might help. But I suggest you ask these questions using the launchpad question facility, some mailing list, or similar.

And I thought I was being so clear.. :(

Forget VB for a minute..
Currently my Keyboard model is Generic 102 (was previously 105).
My layouts are USA Mac and Germany (thought I haven't yet used that layout - so in essence, we're only concerned with USA MAC (which is setup as default and which is working).

If I change the Keyboard model to Apple/MacBook/MacBook Pro - this is when I get the error reported in this bug.
(Although the keyboard continues to work otherwise fine)

That's all with the inbuilt keyboard. The external one is only a work around for the VB issue. That's why I attached to this bug (forget my other issues :)

OK, now gladly disregarding VB and your external keyboard. My advice is to
1. change keyboard layout from "USA Mac" to "USA" and
2. change keyboard model from "Generic" to "Apple/MacBook/MacBook Pro".
Order is relevant if you want to avoid error messages in between.

If that works for you, then bug 327963 applies. If not, contents of ~/.xsession-errors could be useful.

Martin

Thank you very much! I have done that - and there is now no annoying error message. Even if I add a second layout (German). Even if I add the second layout as German-Mac :) :)

So, I'll leave this bug and join the other?

Now I just have to find why my keyboard isn't passed back to my host in VB.. I love linux :D

I encountered the same problem with my integrated MacBookPro keyboard. It's very annoying to get this error message. From usability point of view, this bug should be solved to improve the user experience.

RedVivi schrieb:
> I encountered the same problem with my integrated MacBookPro keyboard.

What version of Ubuntu? Have you tried with Karmic?

Have you had a look at your ~/.xsession-errors file, to check whether
there are any messages there related to keyboard layout configuration?

This is on lucid..
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10706000

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/kbd

xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us", "", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us,lk]
 options = [grp grp:alt_caps_toggle,terminate terminate:ctrl_alt_bksp]
 model =

Same thing here on Lucid....after distro upgrade today (31/03/10)

Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10706000

The result of xprop -root | grep XKB:

_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "gb", "", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "gb", "", ""

The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd:

 layouts = [gb,ir]
 options = [grp grp:alt_shift_toggle]
 model =

Since I have this error I can no longer change my layout using keyboard shortcuts ( Alt + Shift in my case )
Also whenever I try to change the shortcut for layout toggle, I am met with the error message. Same message shows up whenever I log in first, from suspension, or from a locked screen. sometimes this error message stacks up to 20 messages when I unlock the screen.

uname -a
Linux xxxxxx 2.6.32-18-generic #27-Ubuntu SMP Fri Mar 26 19:51:10 UTC 2010 i686 GNU/Linux

xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us,ir", ",", "grp:alts_toggle"
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,ir", ",", "grp:alts_toggle"

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us,ir]
 options = [grp grp:alt_shift_toggle]
 model =

cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder75) Fri Mar 12 01:42:27 PST 2010

Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "kbd"
EndSection

Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DPMS"
EndSection

Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
        Depth 24
    EndSubSection
EndSection

I have removed Iran keyboard layout and the error message has disappeared but if I try to add it back I get the same message. I can add almost any other layout that I want though! Could it be a bug in Iran layout only?

For now I'm using the Afghanistan layout instead as it's similar.

Sennaista, you might want to have a look at ~/.xsession-errors, see if there is an error message in there that might be related to your keyboard layout configuration.

Martin, this is the only relevant item in there:

** (gnome-settings-daemon:1279): WARNING **: Could not activate the XKB configuration

It went bad to worse ...no keyboard in x..keyboard stopped working at gdm login..After using on screen keyboard I logged in but every time I try to change keyboard pref it gives me

Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10706000

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/kbd

This is on lucid..now lucid totally unusable :-(

las, see my above post (#85) and maybe remove the secondary keyboard layout and see what happens?

Thanx Sennaista it worked.Thats the strangest thing. I tried that earlier but didn't work.I added Sri lanka and error msg came back.But kb worked till I re started.After reboot no kb.Had to remove Sri Lanka again.

It only gives you an error msg till you apply it system wide(in kb preferances).If you apply it system wide kb stops working

Some more info from my .xsession-errors:

** (nm-applet:1402): DEBUG: foo_client_state_changed_cb
Error: Error interpreting include file "ir"
                  Exiting
                  Abandoning symbols file "(null)"

** (gnome-settings-daemon:1378): WARNING **: Could not activate the XKB configuration

I guess the problem is with "ir" file, right?

Ok, I solved my problem.

After seeing the above message (#93) I over-wrote the "/usr/share/X11/xkb/symbols/ir" file in my Lucid machine with one copied over from a Karmic machine and the error message has gone away. I can use both "gb-en" and "ir" layouts now! So the "ir" file in Lucid is broken and probably any other layout that throws up the same message too.

las, maybe try what I did with Sri Lanka layout and see what you get.

To myself, Sennaista and las:

It seems this particular bug report has little to do with the problem we are having except the error message. As Sennaista pointed out there is a problem with the symbols file, someone else has already found the minor syntax errors which caused this, here is the bug report:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/553401

Hopefully this issue gets some attention soon.

Right after upgrading to lucid-desktop-amd64-beta2 from karmic-desktop, several dialog boxes with "Error activating XKB configuration" message appear, prompting me to include the following in the bug report.

dragon@hostname:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us", "alt-intl", "lv3:ralt_switch"
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "alt-intl", "lv3:ralt_switch"

dragon@hostname:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us alt-intl,in bolnagri]
 options = [grp grp:alts_toggle,grp grp:alt_shift_toggle]
 model = logiex110

Sennaista, could you please attach the correct/old ir layout?

ir keyboard for 9.04 attached.
this file will fix the error for Persian keyboard!

I had the same problem in Lucid beta2 64AMD with Kurdish Variant
xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "dk", "", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "dk", "", "grp:alt_shift_toggle"
sia@sia-desktop:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [dk,iq ku_ara]
 options = [grp grp:alt_shift_toggle]
 model =

and solved with installing this XKB-DATA-bugfix her:
https://launchpad.net/~skhome/+archive/xkb-data-bugfix/+packages

Sorry Omid, just seen this. Glad you found a working version.

I got this bug on Lucid Lynx. I installed the Beta 1 and I have upgraded until final version.

Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10706000

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/kbd

My results:

adorilson@vmware:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us", "mac", "lv3:ralt_switch"
_XKB_RULES_NAMES(STRING) = "evdev", "apple_laptop", "us", "mac", "lv3:ralt_switch"
adorilson@vmware:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 options = []
 model = macbook79

This Ubuntu is installed on VMware 3.0 and the host is Mac OS X 10.5.8.

Do you need anymore information?

This report has become quite messy and requires clean up,
1. The title and description need update; they refer to issues that probably existed in Edgy but not anymore.
2. In these 100+ comments, there are several different issues mixed together, which makes it even more improbable that they will get attention.
3. What I'll do is close this report and invite you to open new individual bug reports for each separate issue.
When filing a new bug report, please select the xkeyboard-config package.

Some guidelines
a. You should not need to edit xorg.conf in order to configure the keyboard layout. If you have to, then you applied a workaround. The problem is still a bug and requires to be fixed. All configuration should be done in the UI so that it is correct. If not, file a report.
b. You can extract the Ubuntu keyboard configuration for layouts with
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
c. You can test different configurations using the setxkbmap command; you need to create a 'setxkbmap' line using the information from [b]. For example,
setxkbmap -layout us -model macbook79 -variant intl -print | xkbcomp - :0
shows an error which says what the problem is about.

So, please read this post carefully and create new reports where required.