xprop -root | grep XKB says ---- _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "de", "mac_nodeadkeys", "" _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "de", "mac_nodeadkeys", "" ---- . which suggests indigestion in that area??? Now I have the Polish qwerty keyboard I need - however I get a warning message when gnome starts. The message appears nevertheless as soon as control is passed from gdm to the normal user session. http://axishost.net/error-activating/error-activating-xkb-configuration-centos-6-2.php
I can't find any such layout, neither in the gnome config, nor in xkeyboard-config. Since this is a pure CentOS 4.5 install I think the problem can be reproduced easily. The external one is only a work around for the VB issue. Can it!? check this link right here now
Instead, in the line Option "XkbLayout" "ie" I changed ie to pl. I see that you are using nVidia's binary-only driver. Error activating XKB configuration. Notes Issue History Date Modified Username Field Change 2013-09-24 02:02 ojtibi New Issue Issue History Powered by MantisBT Copyright © 2000 - 2016 MantisBT Team Contact administrator for assistance Arch Linux
Also when one goes to customise the keyboard in Gnome hardware preferences (for instance adding an extra keyboard layout) the message also shows up. Here's the repaired link: http://forums.fedoraforum.org/showth...hlight=russian See if the info there helps. Did you set this manually in the configuration tool or was it autodetected? Affecting: control-center (Ubuntu) Filed here by: Bryce Harrington When: 2007-06-14 Assigned: 2007-06-25 Completed: 2007-08-06 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix
Otherwise the system creates a new environment and gets screwed up in the process. That can't be right. If I change the Keyboard model to Apple/MacBook/MacBook Pro - this is when I get the error reported in this bug. (Although the keyboard continues to work otherwise fine) That's all [email protected]:~$ 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" [email protected]:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [us alt-intl,in bolnagri] options =
Exiting? ? ? ? ? ? ? ? ? So I guess you could say that Xming is the problem. this file will fix the error for Persian keyboard! So what do you need to know?
All configuration should be done in the UI so that it is correct. https://bugzilla.redhat.com/show_bug.cgi?id=483195 As far as the pounds symbol is concerned no change, all I get is 3 whether it is shifted or not. All I get is a plain 3! Join Date Jul 2007 Location East Anglia, UK Beans 76 DistroUbuntu 12.04 Precise Pangolin [SOLVED] Error activating XKB configuration I notice the GBP symbol (SHIFT+3) wasn't working on my keyboard, just
You can test different configurations using the setxkbmap command; you need to create a 'setxkbmap' line using the information from [b]. http://axishost.net/error-activating/error-activating-xkb-configuration.php We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Look at this thread.Of course replace keymap code with yours. [email protected]:~$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "abnt2", "br", "", "" _XKB_RULES_NAMES(STRING) = "xorg", "abnt2", "br", "", "grp:alts_toggle" [email protected]:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [br] model = abnt2 options
Sia Neriman (sia-neriman) wrote on 2010-04-11: #99 I had the same problem in Lucid beta2 64AMD with Kurdish Variant xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "dk", "", "" spbrereton (simon-brereton) wrote on 2009-09-17: #78 Martin Thank you very much! There is also no problem when when the X server is on a remote Centos box. http://axishost.net/error-activating/error-activating-xkb-configuration-red-hat.php Even if I add a second layout (German).
My advice is to 1. Ubuntu still interprets the key-presses correctly. Does anyone have other ideas?Thanks.-AP_ Top apara Posts: 7 Joined: 2005/06/04 19:06:37 Contact: Contact apara Website Re: Error activating XKB configuration with VNC Quote Postby apara » 2005/06/04 21:24:58 Looks like
Is it a Mac keyboard, or some other, more PCish keybord? However, if I simply start VNCSERVER before logging in, I get this error message.After this error message, the mouse does not seem to work correctly (the right click menu is missing) Join Date Jul 2007 Location East Anglia, UK Beans 76 DistroUbuntu 12.04 Precise Pangolin Re: Error activating XKB configuration *bump* Any help please? Error activating XKB configuration.
The help file does not list this and using some of the options that might work no improvement is achieved. From usability point of view, this bug should be solved to improve the user experience. Regarding the last update to this issue, please use bug #6679 for further input. navigate to this website Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions.
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 raketenman (sesselastronaut) wrote on 2009-07-23: #69 same in jaunty: xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "ch", "de_mac", "" _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "ch", "de_mac", "" gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd Perhaps we need something more similar to RHEL/FC 'system-config-keyboard'? thanks in advance and for all the great work on this OS.
This was where I ran into this bug. I am hoping that it is not a hardware bug that stops the 3 key from seeing the Shift signal, but that does not explain the absenceof the bar does it? 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. The result is probably not optimal, though, as that configuration is intended to simulate mac-like behaviour on a non-mac keyboard.
I added the keyboard indicator to a panel - right clicking and asking 'show current layout' produces an empty screen. The way to clean it up is sort of gross: su -c "gconftool-2 --config-source=xml:readwrite:/var/lib/gdm/.gconf --unset /apps/gdm/simple-greeter/recent-layouts --direct" rm -f ~/.dmrc gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard/kbd Need to figure out if there's a way If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb thanks Dan fails View Comment 26 Matthieu Araman 2009-04-13 19:52:00 EDT with rawhide updated for today, after applying above command to reset config, still have the same error message.
Have you had a look at your ~/.xsession-errors file, to check whether there are any messages there related to keyboard layout configuration? Comment 35 Need Real Name 2009-04-28 13:31:38 EDT Of course. In Feisty I do not have the same Polish keyboard - it is qwertz instead with Polish diacritics in different places. 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.
None, the status of the bug is updated manually. Very, very, very, very, very, very annoying. http://forums.fedoraforum.org/showth...&highlight=xkb According to some google-results it has something to do with the gnome settings not being the same as the X-server settings.