"Error activating XKB configuration." - Requires manual xorg.conf editing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mactel Support |
Invalid
|
Undecided
|
Unassigned | ||
control-center (Ubuntu) |
Invalid
|
Low
|
Ubuntu Desktop Bugs | ||
xkeyboard-config (Fedora) |
Won't Fix
|
Low
|
|||
xkeyboard-config (Ubuntu) |
Invalid
|
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_
_XKB_RULES_
and
rados@domowy:~$ gconftool-2 -R
/desktop/
layouts = []
model =
overrideSettings = true
options = []
See https:/
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 : | #1 |
Bloch (aidenoreilly) wrote : | #2 |
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 : | #3 |
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
Radek Wisniewski (radwis) wrote : Re: [Bug 67188] Re: Lack of Polish diacritic symbols during writting, no Polish keyboard activated | #4 |
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:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Pozdrawiam
Radek
description: | updated |
description: | updated |
Christer Edwards (christer.edwards) wrote : | #5 |
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/
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-
Bryce Harrington (bryce) wrote : | #6 |
Christer, thanks for the research into this. Yes, it does sort of sound like maybe gnome-keyboard-
Stormhierta (stormhierta) wrote : Re: [Bug 67188] Re: "Error activating XKB configuration." - Requires manual xorg.conf editing | #7 |
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-
> 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:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
--
Andreas Rönnqvist
<email address hidden>
<><><><
www.dreamscarre
www.omegaproject.se
Sebastien Bacher (seb128) wrote : | #8 |
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 : | #9 |
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 |
Mikko Ohtamaa (mikko-red-innovation) wrote : | #10 |
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/
moo@valko:~$ gconftool-2 -R /desktop/
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_
_XKB_RULES_
moo@valko:~$ gconftool-2 -R /desktop/
Mikko Ohtamaa (mikko-red-innovation) wrote : | #11 |
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 : | #12 |
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 : | #13 |
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/
shirish@
_XKB_RULES_
_XKB_RULES_
shirish@
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@
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Description
+++-===
un xkeyboard-conf <none> (no description available)
which shows that xkeyboard-conf is uninstalled
doing a search shows me this :-
shirish@
p xkeyboard-config - Transitional package for xkb-data
then did a search for xkb-data
shirish@
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 : | #14 |
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 : | #15 |
Same problem reported with Rev. A 1998 iMac in Gutsy (these problems did not occur in Feisty):
_XKB_RULES_
_XKB_RULES_
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 : | #16 |
I can confirm this after updating to newest xkb-data.
gnome-keyboard-
dpy: 0x80776b8
evt/error/
Shirish Agarwal (shirishag75) wrote : | #17 |
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 : | #18 |
Same here with a "brazilian portuguese" keyboard with "abnt2" variant.
marcos@
_XKB_RULES_
_XKB_RULES_
marcos@
layouts = [br]
model = abnt2
options = [grp grp:alts_toggle]
overrideSettings = true
marcos@
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 : | #19 |
Same here using gutsy with all updates
rafael@
_XKB_RULES_
_XKB_RULES_
rafael@
layouts = []
model =
options = [lv3 lv3:ralt_
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 : | #20 |
I can confirm that reverting to feisty's version of the package works fine and fixes the problem.
davidc (scienceinthegreen) wrote : | #21 |
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 (pgdx) wrote : | #22 |
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/
pgd@pgd-laptop:~$ xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
pgd@pgd-laptop:~$ gconftool-2 -R /desktop/
layouts = []
model = pc101
overrideSettings = true
options = []
pgd@pgd-laptop:~$
jlinkels (jlinkels) wrote : | #23 |
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 : | #24 |
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.
Magnus Malmsten (magnus-malmsten) wrote : | #25 |
- Skärmbild-Configure - KDE Control Module.png Edit (48.3 KiB, image/png)
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/
xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
gconftool-2 -R /desktop/
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 : | #26 |
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-
Have a look at Bug #188171
This bug was fixed in the package gnome-settings-
Magnus Malmsten (magnus-malmsten) wrote : | #27 |
- Skärmbild-Tangentbordsinställningar.png Edit (34.0 KiB, image/png)
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_
_XKB_RULES_
and here is the output for "gconftool-2 -R /desktop/
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 : | #28 |
- Xorg.1.log Edit (39.2 KiB, text/plain)
I confirm this too. After system rebooting I have to go on System>
mabovo@macbook:~$ xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
mabovo@macbook:~$ gconftool-2 -R /desktop/
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(
Option "XkbLayout" "pt"
Option "XkbVariant" "mac"
# Option "XkbOptions" "lv3:ralt_
EndSection
[ 25.821317] input: Apple Computer Apple Internal Keyboard / Trackpad as /devices/
[ 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/
[ 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/
[ 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/
mabovo (mabovo) wrote : | #29 |
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_
_XKB_RULES_
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "apple_laptop"
# Option "XkbModel" "macintosh(
Option "XkbLayout" "us"
# Option "XkbLayout" "pt"
Option "XkbVariant" "basic"
# Option "XkbVariant" "apple_laptop"
# Option "XkbVariant" "mac"
Option "XkbOptions" "grp_led:scrol l,compose:
EndSection
Evgeny Remizov (ram3ai) wrote : | #30 |
Happened to me after last Hardy Alpha kernel update.
$ xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
$ gconftool-2 -R /desktop/
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_
EndSection
What can be wrong with this config?
André Barmasse (barmassus) wrote : | #31 |
Same problem here after yesterday's hardy update.
Very, very, very, very, very, very annoying.
Outpput of gconftool-2 -R /desktop/
layouts = []
model =
overrideSettings = true
options = []
Output of _xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
Will try to edit xorg.conf manually. Let's hope it works, damn it.
André Barmasse (barmassus) wrote : | #32 |
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
Przemek K. (azrael) wrote : | #33 |
Possible duplicates or related bugs:
Bug #210734
Bug #207812
Bug #209493
Bug #210893
Bug #215699
Bug #217568
Bug #210140
Bug #120420
Yasio (yasio-tomek) wrote : | #34 |
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/
it always shows when i run system.
tomek@tomek-
_XKB_RULES_
_XKB_RULES_
tomek@tomek-
layouts = [pl pl]
model =
options = [grp grp:alts_toggle]
overrideSettings = true
Magnus Malmsten (magnus-malmsten) wrote : | #35 |
I installed Hardy on a clean harddisk. This fixed the keyboard problems for me.
In Red Hat Bugzilla #446684, Eelco (eelco-redhat-bugs) wrote : | #103 |
Description of problem:
[Actually, the problem occurs in gnome-keyboard-
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-
How reproducible:
1. start gnome-keyboard-
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/
================
Additional info:
Hardware: Macbook (late 2006 model)
In Red Hat Bugzilla #446684, Eelco (eelco-redhat-bugs) wrote : | #104 |
Created attachment 305510
screenshot of the error message
In Red Hat Bugzilla #446684, Eelco (eelco-redhat-bugs) wrote : | #105 |
$ xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
$ gconftool-2 -R /desktop/
layouts = []
model = macbook79
options = [Compose key compose:rwin]
overrideSettings = true
In Red Hat Bugzilla #446684, Lubomir (lubomir-redhat-bugs) wrote : | #106 |
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-
In Red Hat Bugzilla #446684, Eelco (eelco-redhat-bugs) wrote : | #107 |
$ rpm -qf --qf %{name}\\n $(which gnome-keyboard-
control-center
In Red Hat Bugzilla #446684, Jose (jose-redhat-bugs) wrote : | #108 |
I'm having the same problem (MacBook with a Portuguese keyboard layout):
$ xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
$ gconftool-2 -R /desktop/
layouts = [pt mac,pt]
model = macbook79
options = [grp grp:alts_toggle]
overrideSettings = true
/jpo
WillSmith (undertakingyou) wrote : | #36 |
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 : | #37 |
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.
In Red Hat Bugzilla #446684, Peter (peter-redhat-bugs) wrote : | #109 |
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"
If this used to work, or you think it should work, please file a bug on upstream bugzilla: https:/
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).
oss_test_launchpad (oss-test-launchpad) wrote : | #38 |
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/
----
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_
_XKB_RULES_
----
.
gconftool-2 -R /desktop/
----
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 : | #39 |
Same problem here on Hardy:
xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
gconftool-2 -R /desktop/
layouts = [de_ch de_ch,ch de_nodeadkeys]
model =
overrideSettings = false
options = [grp grp:alts_toggle]
oss_test_launchpad (oss-test-launchpad) wrote : | #40 |
Problem remains after newest available updates.
Jean-Luc Boss (jlb74) wrote : | #41 |
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
oss_test_launchpad (oss-test-launchpad) wrote : | #42 |
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).
JLB (news-eserver) wrote : | #43 |
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.
oss_test_launchpad (oss-test-launchpad) wrote : | #44 |
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:/
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://
Gerhard Klünger (g-kluenger) wrote : | #45 |
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/
=================
Here are the results:
_XKB_RULES_
_XKB_RULES_
The result of gconftool-2 -R /desktop/
layouts = []
model = btc5126t
overrideSettings = true
options = []
Gruss, Gerhard
In Red Hat Bugzilla #446684, Matěj (matj-redhat-bugs) wrote : | #110 |
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.
egarcia (erikgf) wrote : | #46 |
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-
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
.Ru (vodarus) wrote : | #47 |
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/
xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
gconftool-2 -R /desktop/
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_
EndSection
Keyboard Layouts not working after update to Intrepid.
In Red Hat Bugzilla #446684, Jose (jose-redhat-bugs) wrote : | #111 |
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_
_XKB_RULES_
gconftool-2 (same command line as in comment #5)
-----------
layouts = []
model = macbook79
overrideSettings = true
options = []
In Red Hat Bugzilla #446684, Peter (peter-redhat-bugs) wrote : | #112 |
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.
oss_test_launchpad (oss-test-launchpad) wrote : | #48 |
Is anyone going to hand over this information to the developers?
Btw. I think this is related with https:/
In Red Hat Bugzilla #446684, Joachim (joachim-redhat-bugs) wrote : | #113 |
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"
In Red Hat Bugzilla #446684, Peter (peter-redhat-bugs) wrote : | #114 |
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://
keycode 104 is defined as KEY_KPENTER in /usr/include/
* X keycodes are kernel keycodes + 8.
neub (benpaka) wrote : | #49 |
This bug appears to me on intrepid (ubuntu 8.10)
root@Acer:~# xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
root@Acer:~# gconftool-2 -R /desktop/
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
neub (benpaka) wrote : | #50 |
The command setxkbmap works for me but I've an error at each startup of gnome.
Bryce Harrington (bryce) wrote : | #51 |
This bug is very, very widespread so bumping up the priority another notch.
description: | updated |
Changed in xkeyboard-config: | |
importance: | High → Critical |
status: | Confirmed → Triaged |
In Red Hat Bugzilla #446684, Alex (alex-redhat-bugs) wrote : | #115 |
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-
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/
[alex@Porthos ~]$ xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
[alex@Porthos ~]$
[alex@Porthos ~]$ gconftool-2 -R /desktop/
layouts = [us mac]
model = macbook78
options = [grp grp:shift_
[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
In Red Hat Bugzilla #446684, Peter (peter-redhat-bugs) wrote : | #116 |
please attach the output of setxkbmap -print
In Red Hat Bugzilla #446684, Alex (alex-redhat-bugs) wrote : | #117 |
[alex@Porthos ~]$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us(
xkb_geometry { include "pc(pc104)" };
};
[alex@Porthos ~]$
In Red Hat Bugzilla #446684, Peter (peter-redhat-bugs) wrote : | #118 |
setxkbmap -layout "us(mac)" -model "macbook78"
does this command work without complaints?
In Red Hat Bugzilla #446684, Alex (alex-redhat-bugs) wrote : | #119 |
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.)
In Red Hat Bugzilla #446684, Thomas (thomas-redhat-bugs) wrote : | #120 |
How to get a working "at" and "pipe" sign on my german macbook pro?
John Pugh (jpugh) wrote : | #52 |
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.
Changed in mactel-support: | |
status: | New → Confirmed |
Culip (nate-culip) wrote : | #53 |
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/
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.
jeswin (jeswin) wrote : | #54 |
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
Changed in xkeyboard-config: | |
status: | Unknown → In Progress |
In Red Hat Bugzilla #446684, Axel (axel-redhat-bugs) wrote : | #121 |
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_
_XKB_RULES_
gconf-tool result :
layouts = [fr mac]
model = macintosh
options = []
By the way, why the keymaps list at login screen, in the gnome-keyboard-
In Red Hat Bugzilla #446684, Axel (axel-redhat-bugs) wrote : | #122 |
Checking a box for in agency options (Third level choosers by example)triggers the same error window.
Stewart Johnston (stooj) wrote : | #55 |
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.
Vincenzo Mazzotta (vincenzo-mazzotta-it) wrote : | #56 |
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/
xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
gconftool-2 -R /desktop/
layouts = []
model =
options = [lv3 lv3:ralt_
Thank you for your help :)
Kind Regards
Vincenzo
Vincenzo Mazzotta (vincenzo-mazzotta-it) wrote : | #57 |
Excuse me but not add an important information.
I have a spanish keyboard ;)
Joachim (joachimrs) wrote : | #58 |
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_
_XKB_RULES_
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?)
Spoilerhead (spoilerhead) wrote : | #59 |
up to date intrepid 64bit
_XKB_RULES_
layouts = []
model =
options = []
horribly annozying
Spoilerhead (spoilerhead) wrote : | #60 |
fixed it for me
turned out my /usr/share/
had to reinstall xkb-data
maybe a bug in ext3? as the last shutdown was 100% for sure a clean one
Martin von Gagern (gagern) wrote : | #61 |
- Install debug wrapper around xkbcomp Edit (1.7 KiB, text/x-sh)
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 DownloadedScrip
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.
Sergey V. Udaltsov (sergey-udaltsov) wrote : | #62 |
What I'd recommend is building libxklavier and trying tests/test_config app - trying to set the required configuration.
Changed in xkeyboard-config: | |
assignee: | nobody → canonical-desktop-team |
Martin Pitt (pitti) wrote : | #63 |
Bryce, can you take a look at this, please?
Changed in xkeyboard-config: | |
assignee: | canonical-desktop-team → bryceharrington |
Bryce Harrington (bryce) wrote : | #64 |
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.
Rick Spencer (rick-rickspencer3) wrote : | #65 |
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.
Changed in xkeyboard-config: | |
importance: | Critical → Medium |
Changed in xkeyboard-config: | |
assignee: | bryceharrington → nobody |
Sebastien Bacher (seb128) wrote : | #66 |
Sergey hinted to rebuild libxklaver and try test_config, could somebody having the issue do that?
oss_test_launchpad (oss-test-launchpad) wrote : | #67 |
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.
In Red Hat Bugzilla #446684, Bug (bug-redhat-bugs) wrote : | #123 |
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://
In Red Hat Bugzilla #446684, Bug (bug-redhat-bugs) wrote : | #124 |
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 |
Martin von Gagern (gagern) wrote : | #68 |
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.
raketenman (sesselastronaut) wrote : | #69 |
same in jaunty:
xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
gconftool-2 -R /desktop/
layouts = []
options = [altwin altwin:super_win]
model = macbook79
.xsession-errors;
...
(gnome-
Error: No Symbols named "de_mac" in the include file "macintosh_vndr/ch"
** (gnome-
....
hth
h
Martin von Gagern (gagern) wrote : | #70 |
-----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://
iEYEARECAAYFAkp
cEoAnjLmPOolFNB
=x4FP
-----END PGP SIGNATURE-----
raketenman (sesselastronaut) wrote : | #71 |
jep that's it - changed keyboard model to generic 102 & layout to Switzerland German (Macintosh) worked for me!
thanks
spbrereton (simon-brereton) wrote : | #72 |
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!?
Martin von Gagern (gagern) wrote : | #73 |
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_
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.
spbrereton (simon-brereton) wrote : | #74 |
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?
Martin von Gagern (gagern) wrote : | #75 |
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.
spbrereton (simon-brereton) wrote : | #76 |
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/
(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 :)
Martin von Gagern (gagern) wrote : | #77 |
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/
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.
spbrereton (simon-brereton) wrote : | #78 |
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
RedVivi (redvivi) wrote : | #79 |
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.
Martin von Gagern (gagern) wrote : | #80 |
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?
las (bandara-ls) wrote : | #81 |
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/
xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
gconftool-2 -R /desktop/
layouts = [us,lk]
options = [grp grp:alt_
model =
Sennaista (sennaista) wrote : | #82 |
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_
_XKB_RULES_
The result of gconftool-2 -R /desktop/
layouts = [gb,ir]
options = [grp grp:alt_
model =
Hassanakevazir (hassanakevazir) wrote : | #83 |
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_
_XKB_RULES_
gconftool-2 -R /desktop/
layouts = [us,ir]
options = [grp grp:alt_
model =
Hassanakevazir (hassanakevazir) wrote : | #84 |
cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@
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
Sennaista (sennaista) wrote : | #85 |
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?
Sennaista (sennaista) wrote : | #86 |
For now I'm using the Afghanistan layout instead as it's similar.
Martin von Gagern (gagern) wrote : | #87 |
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.
Sennaista (sennaista) wrote : | #88 |
Martin, this is the only relevant item in there:
** (gnome-
las (bandara-ls) wrote : | #89 |
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/
This is on lucid..now lucid totally unusable :-(
Sennaista (sennaista) wrote : | #90 |
las, see my above post (#85) and maybe remove the secondary keyboard layout and see what happens?
las (bandara-ls) wrote : | #91 |
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 : | #92 |
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 : | #93 |
Some more info from my .xsession-errors:
** (nm-applet:1402): DEBUG: foo_client_
Error: Error interpreting include file "ir"
** (gnome-
I guess the problem is with "ir" file, right?
Sennaista (sennaista) wrote : | #94 |
Ok, I solved my problem.
After seeing the above message (#93) I over-wrote the "/usr/share/
las, maybe try what I did with Sri Lanka layout and see what you get.
Hassanakevazir (hassanakevazir) wrote : | #95 |
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:/
Hopefully this issue gets some attention soon.
Sonny (aadityabhatia) wrote : | #96 |
Right after upgrading to lucid-desktop-
dragon@hostname:~$ xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
dragon@hostname:~$ gconftool-2 -R /desktop/
layouts = [us alt-intl,in bolnagri]
options = [grp grp:alts_toggle,grp grp:alt_
model = logiex110
Omid Mottaghi (omidmottaghi) wrote : | #97 |
Sennaista, could you please attach the correct/old ir layout?
Omid Mottaghi (omidmottaghi) wrote : | #98 |
Sia Neriman (sia-neriman) wrote : | #99 |
I had the same problem in Lucid beta2 64AMD with Kurdish Variant
xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
sia@sia-desktop:~$ gconftool-2 -R /desktop/
layouts = [dk,iq ku_ara]
options = [grp grp:alt_
model =
and solved with installing this XKB-DATA-bugfix her:
https:/
Sennaista (sennaista) wrote : | #100 |
Sorry Omid, just seen this. Glad you found a working version.
Adorilson (adorilson) wrote : | #101 |
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/
My results:
adorilson@vmware:~$ xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
adorilson@vmware:~$ gconftool-2 -R /desktop/
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 : | #102 |
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/
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 |
In Red Hat Bugzilla #446684, Philip (philip-redhat-bugs) wrote : | #125 |
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/
---
$ xprop -root | grep XKB
_XKB_RULES_
_XKB_RULES_
$ gconftool-2 -R /desktop/
layouts = [us mac,us intl]
options = [grp grp:shift_
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).
In Red Hat Bugzilla #446684, Peter (peter-redhat-bugs) wrote : | #126 |
reopening per comment 22
In Red Hat Bugzilla #446684, Filip (filip-redhat-bugs) wrote : | #127 |
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_
_XKB_RULES_
filip@cowfarm:~
$ gconftool-2 -R /desktop/
layouts = [us]
options = [grp grp:shift_
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/
In Red Hat Bugzilla #446684, Peter (peter-redhat-bugs) wrote : | #128 |
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 |
after searching the forums, I modified the xorg.conf and hashed the line:
# Option "XkbVariant" "qwerty"
It helped, everything seems to be ok.