flz 1 – 0 libxklavier
I’d like to kick in the butt that guy who decided that setting XKB_BIN_BASE to XKB_BASE as default was a good idea.
If you’re using X.org 7.2 from the experimental tree and you tried to use anything special in keyboard properties, you probably got an XKB error. I spent a significant amount of time trying to find that bug, and I just noticed that, for some reason, libxklavier tried to execute /usr/X11R6/share/X11/xkb/xkbcomp. WTF!! So using the right configure switch (—with-xkb-bin-base=${X11BASE}/bin) it’s fixed.
One showstopper down. We’re not too far from the holy day.
PS: I somewhat decided that we’ll do the PREFIX merge at the same time that we’ll commit the new X.org so it’s likely to delay the merge a bit.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
February 2nd, 2007 - 19:14
Well, at least you found it !
Do you have, by chance, a list with showstoppers ?
February 3rd, 2007 - 21:58
Nope, still have to think about this. I have to fix nvidia-driver for a start.
February 4th, 2007 - 04:10
I have problems with keybinding since I have updated my ports today. I see the following in Xorg.0.log:
(**) Keyboard1: XkbModel: “pc105”
(**) Option “XkbLayout” “us”
(**) Keyboard1: XkbLayout: “us”
(**) Option “CustomKeycodes” “off”
(**) Keyboard1: CustomKeycodes disabled
(II) XINPUT: Adding extended input device “Keyboard1” (type: KEYBOARD)
(II) XINPUT: Adding extended input device “Mouse1” (type: MOUSE)
(WW) Couldn’t load XKB keymap, falling back to pre-XKB keymap