[SOLVED] What's causing these xkbcomp warnings after latest -current updates?

ljb643 · 06-17-2021, 06:59 PM

These started showing up after the most recent updates to Slackware64-current. Possible cause is the upgrade to xkeyboard-config-2.33. I get a block of 137 of these warnings, then a repeat. Mostly I use the xdm login manager, so they show up in /var/log/xdm.log, but if I use startx then they show up in the output of that command. They are not user-specific - when using xdm they are ouptut before anyone logs in.

They are apparently harmless, just annoying. Any ideas what is wrong here?

Code:

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86BrightnessAuto
> Warning:          Could not resolve keysym XF86DisplayOff
> Warning:          Could not resolve keysym XF86Info 
> Warning:          Could not resolve keysym XF86AspectRatio
> Warning:          Could not resolve keysym XF86DVD
...(etc, total 137 lines)

phenixia2003 · 06-18-2021, 02:27 AM

Quote:

Originally Posted by ljb643

These started showing up after the most recent updates to Slackware64-current. Possible cause is the upgrade to xkeyboard-config-2.33. I get a block of 137 of these warnings, then a repeat. Mostly I use the xdm login manager, so they show up in /var/log/xdm.log, but if I use startx then they show up in the output of that command. They are not user-specific - when using xdm they are ouptut before anyone logs in.

They are apparently harmless, just annoying. Any ideas what is wrong here?

Code:

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86BrightnessAuto
> Warning:          Could not resolve keysym XF86DisplayOff
> Warning:          Could not resolve keysym XF86Info 
> Warning:          Could not resolve keysym XF86AspectRatio
> Warning:          Could not resolve keysym XF86DVD
...(etc, total 137 lines)

Seems related to this :

Quote:

Whenever xkeyboard-config is newer than xorgproto, or libX11 just hasn't yet been rebuilt against the protocol we end up with some unresolved symbols. That's not an error, it just happens[...]

--
SeB

ljb643 · 06-18-2021, 09:22 PM

Yes that's it, thanks.

(I'm going to use that line from the commit message myself someday: "That's not an error, it just happens".)