Launchpad has imported 26 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=446684.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
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
Desktop Bugs, which is a bug assignee.
--
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
Desktop Bugs, which is a bug assignee.
--
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
Desktop Bugs,
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
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?
--
Error activating XKB configuration. - Requires manual xorg.conf editing
For now I'm using the Afghanistan layout instead as it's similar.
--
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
Desktop Bugs, which is a bug assignee.
--
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.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received
Martin, this is the only relevant item in there:
** (gnome-settings-daemon:1279): WARNING **: Could not activate the XKB
configuration
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you
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
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.
cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeis...@builder75) Fri Mar 12 01:42:27
PST 2010
Section ServerLayout
Identifier Layout0
Screen 0 Screen0
InputDeviceKeyboard0 CoreKeyboard
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
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
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
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
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
Desktop Bugs, which is a bug
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.
--
** Changed in: xkeyboard-config (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) = (unassigned)
** Tags added: ct-rev
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you are a
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 (Ubuntu)
Importance: Critical = Medium
--
Error activating XKB configuration. -
Sergey hinted to rebuild libxklaver and try test_config, could somebody
having the issue do that?
--
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
Desktop Bugs,
** Changed in: xkeyboard-config (Ubuntu)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
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
Bryce, can you take a look at this, please?
** Changed in: xkeyboard-config (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Bryce
Harrington (bryceharrington)
--
Error activating XKB configuration. - Requires manual xorg.conf editing
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.
--
Error activating XKB configuration. - Requires manual
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
What I'd recommend is building libxklavier and trying tests/test_config
app - trying to set the required configuration.
--
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
macbook1,1
Preferences Keyboard Layout set to macbook/macbookpro. have two layouts (german
and US) activated.
the above mentioned error occurs at every login.
The X.Org Foundation 10502000
xprop:
_XKB_RULES_NAMES_BACKUP(STRING) = evdev, pc105, us, mac,
lv3:ralt_switch
_XKB_RULES_NAMES(STRING)
up to date intrepid 64bit
_XKB_RULES_NAMES_BACKUP(STRING) = base, pc101, us, ,
layouts = []
model =
options = []
horribly annozying
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because
fixed it for me
turned out my /usr/share/X11/xkb/rules directory was empty
had to reinstall xkb-data
maybe a bug in ext3? as the last shutdown was 100% for sure a clean one
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You
Excuse me but not add an important information.
I have a spanish keyboard ;)
--
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
Desktop Bugs, which is a bug
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.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received
** Changed in: xkeyboard-config (Fedora)
Status: Unknown = In Progress
--
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
Desktop Bugs, which is a bug
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
--
Error activating XKB
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
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
This bug is very, very widespread so bumping up the priority another
notch.
** Description changed:
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
The command setxkbmap works for me but I've an error at each startup of
gnome.
--
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
Desktop Bugs, which is a bug
This bug appears to me on intrepid (ubuntu 8.10)
[EMAIL PROTECTED]:~# xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = evdev, pc105, es, latin9,
_XKB_RULES_NAMES(STRING) = evdev, pc105, es, latin9,
[EMAIL PROTECTED]:~# gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
options =
Is anyone going to hand over this information to the developers?
Btw. I think this is related with https://bugs.launchpad.net/xkeyboard-
config/+bug/261573.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received 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
10502000
If you report this situation
u 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
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
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
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).
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification
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.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received
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
--
Error activating XKB configuration. - Requires manual xorg.conf editing
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,chde_nodeadkeys]
model =
Problem remains after newest available updates.
--
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
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
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
I was able to fix this problem by changing the xorg.conf line:
Option XkbVariant[EMAIL PROTECTED]
to
Option XkbVariantbasic
Then the error no longer appeared when loading gnome.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
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.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You
I installed Hardy on a clean harddisk. This fixed the keyboard problems
for me.
--
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
Desktop Bugs, which is a bug
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
Possible duplicates or related bugs:
Bug #210734
Bug #207812
Bug #209493
Bug #210893
Bug #215699
Bug #217568
Bug #210140
Bug #120420
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you are
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) =
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
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
I confirm this too. After system rebooting I have to go on
SystemKeyboardLayout disposition and click on Apple Laptop to have
accentuation working again for brazilian characteres.
[EMAIL PROTECTED]:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = xorg, macintosh(macbook79), pt, mac,
Finally I found the perfect match for MacBook 2nd gen UK keyboard configured
for brazilian portuguese characters:
[EMAIL PROTECTED]:~$ 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
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
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.
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
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.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received
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
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
1030
If you
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
I can confirm that reverting to feisty's version of the package works
fine and fixes the problem.
--
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
Desktop Bugs,
Same here using gutsy with all updates
[EMAIL PROTECTED]:~$ 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
[EMAIL PROTECTED]:~$ gconftool-2 -R
Same here with a brazilian portuguese keyboard with abnt2 variant.
[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
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
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification
changing Driver from kbd to keyboard didn't solve the problem as the
workaround mentioned above also didn't solve it, unfortunately :(
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received this bug notification because you
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
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
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
Selecting finland, macintosh doesn't create the issue on gutsy, could
you try if that's still happening to you on it?
--
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
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:
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.
--
Error activating XKB configuration. - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received
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
Do you have easy steps to trigger the bug? What gconf values did you
change?
** Changed in: control-center (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: New = Incomplete
--
Error activating XKB configuration. - Requires manual xorg.conf
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
1 - 100 of 101 matches
Mail list logo
