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

Bug #67188 reported by Radek Wisniewski on 2006-10-20
398
This bug affects 21 people
Affects Status Importance Assigned to Milestone
Mactel Support
Undecided
Unassigned
control-center (Ubuntu)
Low
Ubuntu Desktop Bugs
xkeyboard-config (Fedora)
Won't Fix
Low
xkeyboard-config (Ubuntu)
Medium
Unassigned

Bug Description

After upgrading to Edgy Eft, the Polish symbols disapeared when I write. However, they are properly displayed at the menus, web pages, etc.. During logging in, the system showed an error message:
"There is an error of configuration activation of the XKB. This could be caused by:
 - error in libxklavier, or X serwera (tools xkbcomp, xmodmap), or serwer X is not comptible with libxkbfile implementation.
Version of serwer X:
The X.Org Foundation
70101000"
 The error message also suggests to run:
rados@domowy:~$ xprop -root | grep XKB

_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "pl", "qwerty", "lv3:ralt_switch"
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "pl", "qwerty", "lv3:ralt_switch"

and
rados@domowy:~$ gconftool-2 -R

/desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 model =
 overrideSettings = true
 options = []

See https://help.ubuntu.com/community/DebuggingXAutoconfiguration for discussion of workarounds for this bug. For more discussion also see http://lists.freebsd.org/pipermail/freebsd-gnome/2005-December/013059.html and http://ubuntuforums.org/showthread.php?t=288974.

A correct solution requires that Preferences > keyboard (or a similar GUI configuration tool) set the keyboard correctly, without requiring editing of xorg.conf. Possibly it will need changed to not update gconf but rather update the xorg.conf file directly.

This problem sometimes is caused by a new xorg that doesn't support the selected XkbVariant for the configured keyboard layout, and the upgrade program doesn't reconfigure xorg.conf (or whatever) correctly to switch to the proper layout.

description: updated
Radek Wisniewski (radwis) wrote :

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

It helped, everything seems to be ok.

Bloch (aidenoreilly) wrote :

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

Bloch (aidenoreilly) 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

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

Bryce Harrington (bryce) on 2007-05-22
description: updated
description: updated

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'?

Bryce Harrington (bryce) wrote :

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

Sebastien Bacher (seb128) wrote :

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

Changed in control-center:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Sebastien Bacher (seb128) wrote :

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.

Changed in control-center:
status: Incomplete → Invalid

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.

Sebastien Bacher (seb128) wrote :

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

Shirish Agarwal (shirishag75) wrote :

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.

Shirish Agarwal (shirishag75) wrote :

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.

Andrew Roazen (andrew-roazen) wrote :

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

FrejSoya (frej) wrote :

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

Shirish Agarwal (shirishag75) wrote :

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

mabovo (mabovo) wrote :

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

Rafael Sachetto (rsachetto) wrote :

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

Michele Campeotto (michelec) wrote :

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

davidc (scienceinthegreen) wrote :

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.

Pål Grønås Drange (drange) wrote :

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:~$

jlinkels (jlinkels) wrote :

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

David Tomaschik (matir) wrote :

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.

pvdeynse (vandeynse) wrote :

             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.

mabovo (mabovo) wrote :

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

mabovo (mabovo) wrote :

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

Evgeny Remizov (ram3ai) wrote :

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?

André Barmasse (barmassus) wrote :

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.

André Barmasse (barmassus) wrote :

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

Yasio (yasio-tomek) wrote :

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.

67 comments hidden view all 128 comments

Description of problem:
[Actually, the problem occurs in gnome-keyboard-properties, but that one was not
in the components list.]
Choosing keyboard layout Macbook/Macbook Pro (Intl) produces an error in Fedora 9.

Version-Release number of selected component (if applicable):
GNOME gnome-keyboard-properties 2.22.1

How reproducible:
1. start gnome-keyboard-properties
2. select layouts tab
3. select keyboard model MacBook/MacBook Pro (Intl)
4. close

Error message:
==============
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
10499901

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

================
Additional info:

Hardware: Macbook (late 2006 model)

Created attachment 305510
screenshot of the error message

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

$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 model = macbook79
 options = [Compose key compose:rwin]
 overrideSettings = true

Eelco: Thank you for reporting the problem, I am reassigning it to the right
component owner.

The following command might be useful to find out which component does the
binary belong to:

$ rpm -qf --qf %{name}\\n $(which gnome-keyboard-properties)

$ rpm -qf --qf %{name}\\n $(which gnome-keyboard-properties)
control-center

I'm having the same problem (MacBook with a Portuguese keyboard layout):

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

$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [pt mac,pt]
 model = macbook79
 options = [grp grp:alts_toggle]
 overrideSettings = true

/jpo

71 comments hidden view all 128 comments
WillSmith (undertakingyou) wrote :

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.

gaulinmp (gaulinmp+ubuntu) wrote :

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.

71 comments hidden view all 128 comments

Eelco:

The problem is that the keysyms for mac don't provide a intl variant. The error can be reproduced on the commandline by running:
setxkbmap -layout us -model macbook79 -variant intl -print | xkbcomp - :0

Error: No Symbols named "intl" in the include file "macintosh_vndr/us"
                  Exiting

If this used to work, or you think it should work, please file a bug on upstream bugzilla: https://bugs.freedesktop.org/enter_bug.cgi?product=xkeyboard-config

Jose:
I can't reproduce your problem. Can you try to run:
setxkbmap -layout pt -model macbook79 -option grp:alts_toggle -print | xkbcomp - :0
and check for an error message. If there is one, please attach it. If there is none, please try if the macbook79 model works with any other layout (e.g. us). If it does, please try to find which setting triggers the error - it could be the layout or the alts_toggle option (unlikely).

70 comments hidden view all 128 comments

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.

Jean-Luc Boss (jlb74) wrote :

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.

69 comments hidden view all 128 comments

Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

Hi,

I'm no longer having problems selecting the MacBook Intl layout with the latest updates installed. However the Portuguese layout still has 2 problematic keys:

 * the characters '<' and '>' are being generated by key positioned left of
   numeric '1'. These characters should be generated by the key immediately left
   of the 'z' key

 * the key that should be generating the '<' and '>' characters is producing
   '`' (backticks) and with the shift key pressed '~' (tildes).

/jpo

xprop output (same command line as in comment #5)
------------
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "pt", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "macbook79", "pt", "", ""

gconftool-2 (same command line as in comment #5)
-----------
 layouts = []
 model = macbook79
 overrideSettings = true
 options = []

can't reproduce that with exactly the same settings. What keycode is sent by the keyboard for the two erroneous keys? Please run xev and attach the log here.
Also, please attach the output of xkbcomp -xkb :0 -
thanks.

Created attachment 322891
Typescript with commands to check XKB settings on german MacBook

On my german MacBook (2nd generation) I had encountered also a similar problem in F8 and F9 that <> and ^° keys are exchanged, as reported by jko in #8, but apparently this is fixed in F10 preview.

However, in F10 preview, the AltGr key (2nd key right to space) does no longer work with macbook79 german keyboard layout and therefore no characters like |,€,@, ~ can be typed in. Apparently because keycode 104 is mapped mistakenly to KP_Enter. I'have created a ~/.Xmodmap with the following line to fix the problem:

keycode 104 = ISO_Level3_Shift

This is working, but when logging in, a "Error activating XKB configuration" error dialog box is reported but this seems to be a false alarm.
Find attached the output of xprop, gconftool and "xkbcomp - :0"

Joachim:
To not confuse this bug with the one you mentioned, please open a new bugreport and copy your comment (and mine) into the new report.

Here's what I need you to do:
please get evtest from http://people.freedesktop.org/~whot/evtest.c, compile it up (gcc -o evtest evtest.c) and run it as "sudo ./evtest /dev/input/eventX" where eventX is the device of your keyboard (/proc/bus/input/devices will tell you). Hit the AltGr key and attach the output to the new bugreport.

keycode 104 is defined as KEY_KPENTER in /usr/include/linux/input.h*, so this may actually be a kernel problem. KEY_RIGHTALT (AltGr) should be keycode 108.

* X keycodes are kernel keycodes + 8.

Bryce Harrington (bryce) on 2008-12-16
description: updated
Changed in xkeyboard-config:
importance: High → Critical
status: Confirmed → Triaged

I'm not sure my problem is strictly related to this bug report, but I am also getting this same error when I try to select a US Macbook layout for my keyboard layout.

I just upgraded to Fedora 10 on my Macbook from Fedora 9. Previously, I never had to select a non-generic keyboard model or non-standard layout. Everything (mostly) worked out of the box, so I never paid much attention to it.

Well, once I upgraded, a bunch of things stopped working (including the arrow keys and higher fn+ keys such as delete and home/end, etc.) so I started trying to find some combination of settings that would fix the problem.

I finally discovered that: a) Setting "USA Macintosh" at the login screen, AND b) Setting keyboard model to "MacBook/MacBook Pro" in System->Preferences->Hardware->Keyboard->Layouts, AND c) Setting my "selected layouts" default to "USA Macintosh" would actually fix the layout. HOWEVER, I always get the following error on logging in:

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
10503000

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

[alex@Porthos ~]$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "base", "evdev", "us", "", ""
_XKB_RULES_NAMES(STRING) = "base", "evdev", "us", "mac", ""
[alex@Porthos ~]$
[alex@Porthos ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us mac]
 model = macbook78
 options = [grp grp:shift_caps_toggle]
[alex@Porthos ~]$

I'm still poking around at this, so I might end up working around this better with some other combination of settings. However, that dialog suggests a bug which should probably be addressed. :-P

Thanks for your time.
--Alex

please attach the output of setxkbmap -print

[alex@Porthos ~]$ setxkbmap -print
xkb_keymap {
 xkb_keycodes { include "evdev+aliases(qwerty)" };
 xkb_types { include "complete" };
 xkb_compat { include "complete" };
 xkb_symbols { include "pc+us(mac)+inet(evdev)" };
 xkb_geometry { include "pc(pc104)" };
};
[alex@Porthos ~]$

setxkbmap -layout "us(mac)" -model "macbook78"

does this command work without complaints?

Yes, if I run that command with my desktop fully loaded, I see no error message either in the terminal or in a dialog box. (Note, however, that by this time I've already seen the error at login, and despite the error the layout seems to take effect.)

How to get a working "at" and "pipe" sign on my german macbook pro?

John Pugh (jpugh) on 2009-01-11
Changed in mactel-support:
status: New → Confirmed
Changed in xkeyboard-config:
status: Unknown → In Progress

Same problem on a MacbookPro 3,1, french azerty keyboard, with an up to date Fedora 10 (fresh installed).

While setting the keymap on the login screen ("macintosh" entry in the list), the keyboard switch to the mac layout, @ and < (and so on...) characters works, but special characters (pipes, brackets) cannot be used.

Using the System > Settings > Hardware > Keyboard tool to switch to an "Apple"/"Macbook Pro (Intl)" (or any other keymaps for "Apple") give the same error. (tried in this "macintosh" session, and in a "latin9" session)

xprop result :
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "fr", "latin9", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "fr", "mac", ""

gconf-tool result :
 layouts = [fr mac]
 model = macintosh
 options = []

By the way, why the keymaps list at login screen, in the gnome-keyboard-properties tool and in the system-config-keyboard are not the same lists ?

Checking a box for in agency options (Third level choosers by example)triggers the same error window.

Changed in xkeyboard-config:
assignee: nobody → canonical-desktop-team
Martin Pitt (pitti) on 2009-03-09
Changed in xkeyboard-config:
assignee: canonical-desktop-team → bryceharrington
Changed in xkeyboard-config:
importance: Critical → Medium
Changed in xkeyboard-config:
assignee: bryceharrington → nobody

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Changed in xkeyboard-config (Fedora):
status: In Progress → Won't Fix
34 comments hidden view all 128 comments
las (bandara-ls) wrote :

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 :-(

Sennaista (sennaista) wrote :

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

las (bandara-ls) wrote :

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.

las (bandara-ls) wrote :

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

Sennaista (sennaista) wrote :

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?

Sennaista (sennaista) wrote :

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.

Aaditya Bhatia (aadityabhatia) wrote :

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

Omid Mottaghi (omidmottaghi) wrote :

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

Omid Mottaghi (omidmottaghi) wrote :
  • ir Edit (9.2 KiB, text/plain)

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

Sia Neriman (sia-neriman) wrote :

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

Sennaista (sennaista) wrote :

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

Adorilson (adorilson) wrote :

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?

Simos Xenitellis  (simosx) wrote :

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.

Changed in mactel-support:
status: Confirmed → Invalid
Changed in xkeyboard-config (Ubuntu):
status: Triaged → Invalid
22 comments hidden view all 128 comments

I can reproduce this bug on Fedora 14, could it please be reopened? Selecting either the "MacBook/MacBook Pro" keyboard model or the "MacBook/MacBook Pro (Intl)" model pops up a dialog box with the following error message:

---
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:
Fedora Project
10901000

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", "intl", ""
_XKB_RULES_NAMES(STRING) = "evdev", "evdev", "us", "intl", ""
$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us mac,us intl]
 options = [grp grp:shift_caps_toggle]
 model = macbook79

In addition, any changes I make to the keyboard _layout_ (not the model) are reverted when I log out and log back in. I'm running Fedora 14 on VirtualBox 3.2.12 r68302 on a MacBook (model MacBook2,1).

reopening per comment 22

I am also getting this error after an upgrade to F14, on a machine accessed through XNclient. There are 3 keyboard layouts set up: US, Serbian and Serbian Latin. The error leaves the keyboard inoperative, with arrow keys, and pgup, pgdn etc inoperational. They report no events when passed to 'xev'.

filip@cowfarm:~
$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc102", "us", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc102", "us", "", ""
filip@cowfarm:~
$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us]
 options = [grp grp:shift_caps_toggle,grp grp:lwin_toggle]
 model =
filip@cowfarm:~
$

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

X server version data:
The X.Org Foundation
60900000

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

This bug was filed against Fedora 14 which is now EOL. Please re-open this bug if you still experience this issue with one of the currently suppported versions of Fedora. Don't forget to update the version field if you do so.

Changed in xkeyboard-config (Fedora):
importance: Unknown → Low
Displaying first 40 and last 40 comments. View all 128 comments or add a comment.