mactel-support team mailing list archive

[Martin von Gagern <martin.vgagern@xxxxxxx>]

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.

-- 
"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 Mactel
Support, which is the registrant for Mactel Support.

Status in Mactel Support: Confirmed
Status in “control-center” package in Ubuntu: Invalid
Status in “xkeyboard-config” package in Ubuntu: Triaged
Status in “xkeyboard-config” package in Fedora: Won't Fix

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

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

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

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


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

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


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