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
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
Sorry Omid, just seen this. Glad you found a working version.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in
Sennaista, could you please attach the correct/old ir layout?
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in
ir keyboard for 9.04 attached.
this file will fix the error for Persian keyboard!
** Attachment added: ir
http://launchpadlibrarian.net/43859696/ir
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug
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
s...@sia-desktop:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts =
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.
dra...@hostname:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = evdev, pc105,
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
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
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
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
las, see my above post (#85) and maybe remove the secondary keyboard
layout and see what happens?
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you are a member of Ubuntu-X,
which is
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.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
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
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you are a
Same thing here on Lucidafter 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
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
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.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
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?
--
Error
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
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
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
OK, now gladly disregarding VB and your external keyboard. My advice is to
1. change keyboard layout from USA Mac to USA and
2. change keyboard model from Generic to Apple/MacBook/MacBook Pro.
Order is relevant if you want to avoid error messages in between.
If that works for you, then bug 327963
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!?
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug
spbrereton, if what you experience is in fact bug #327963, then I
believe that you should set the MODEL to something mac (e.g.
macintosh_vndr/ch) and the LAYOUT to a variant not mentioning mac
(e.g. de, not de_mac).
The reason is that the layout files for mac models simply don't mention
any
same in jaunty:
xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = evdev, pc105, ch, de_mac,
_XKB_RULES_NAMES(STRING) = evdev, pc105, ch, de_mac,
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
options = [altwin altwin:super_win]
model = macbook79
-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
jep that's it - changed keyboard model to generic 102 layout to Switzerland
German (Macintosh) worked for me!
thanks
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you are a member of
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
** Changed in: xkeyboard-config (Fedora)
Status: In Progress = Won't Fix
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
29 matches
Mail list logo
