xkbcomp errors

[Riccardo Mottola]

Hi,

after updating userland, I do get these when starting X11:

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Couldn't lookup keysym
> Symbol interpretation ignored
> Error: Couldn't lookup keysym
> Symbol interpretation ignored
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Couldn't lookup keysym
> Symbol interpretation ignored
> Error: Couldn't lookup keysym
> Symbol interpretation ignored
> 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


it says they are not fatal and generally x11 seems to work, but I wonder
what they are, if they can be sorted out, etc...

Riccardo

[wett...@gmail.com]

> Symbol interpretation ignored

This looks like an unknown keysym being used in xkeyboard-config. That
would be strange if you xproto and libX11 are up to date. Do you see
this also when you run 'setxkbmap -print | xkbcomp - tmp.xkb' ?

> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols

That one is harmless. You can find more details here:

https://bugs.freedesktop.org/show_bug.cgi?id=57242

Andreas

[Riccardo Mottola]

Hi,

wett...@gmail.com wrote:
> This looks like an unknown keysym being used in xkeyboard-config. That
> would be strange if you xproto and libX11 are up to date. Do you see
> this also when you run 'setxkbmap -print | xkbcomp - tmp.xkb' ?

yes, I see it on the stdlog when running your command. Do you need the
generated tmp.xkb ?

setxkbmap -print
xkb_keymap {
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+it+inet(pc105)" };
xkb_geometry { include "pc(pc105)" };
};


Riccardo

[wett...@gmail.com]

> yes, I see it on the stdlog when running your command. Do you need the
> generated tmp.xkb ?

I am not sure that the problematic part is still in there. If running
'xkbcomp tmp.xkb' does show the error, it is, and you can send it.

That said, I think my hypothesis about the error cannot be correct. I
thought a keysym coming in through this line:

xkb_compat { include "complete" };

would generate the warning, but no keysyms where added there recently
(~3 years, upstream), and also this line is what "everybody" uses. If
all your system is up to date, I do not understand what's going on.

Andreas