* [ISSUE] xkbcomp errors
@ 2021-07-09 12:26 dkwo
2021-07-09 13:43 ` ericonr
` (23 more replies)
0 siblings, 24 replies; 25+ messages in thread
From: dkwo @ 2021-07-09 12:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 10013 bytes --]
New issue by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/31870
Description:
```
$ xuname
Void 5.12.14_1 x86_64-musl GenuineIntel uptodate rrnFFFFFFF
$ xbps-query -p pkgver xkbcomp
xkbcomp-1.4.2_1
```
Xorg logs:
```
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: Linux Void
Current Operating System: Linux ajax 5.12.14_1 #1 SMP 1625102948 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-5.12.14_1 root=UUID=802049d2-8957-4735-8ddb-53d09b9bfcd8 ro loglevel=4 rd.luks.name=809df427-d7d5-408c-a195-3be6e86813
33=cryptroot root=/dev/mapper/cryptroot rd.luks.options=discard
Build Date: 18 April 2021 03:55:47AM
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Fri Jul 9 09:46:34 2021
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 256 for name <I256> ignored
> X11 cannot support keycodes above 255.
> This warning only shows for the first high keycode.
> Internal error: Could not resolve keysym XF86BrightnessAuto
> Internal error: Could not resolve keysym XF86DisplayOff
> Internal error: Could not resolve keysym XF86Info
> Internal error: Could not resolve keysym XF86AspectRatio
> Internal error: Could not resolve keysym XF86DVD
> Internal error: Could not resolve keysym XF86Audio
> Internal error: Could not resolve keysym XF86ChannelUp
> Internal error: Could not resolve keysym XF86ChannelDown
> Internal error: Could not resolve keysym XF86Break
> Internal error: Could not resolve keysym XF86VideoPhone
> Internal error: Could not resolve keysym XF86ZoomReset
> Internal error: Could not resolve keysym XF86Editor
> Internal error: Could not resolve keysym XF86GraphicsEditor
> Internal error: Could not resolve keysym XF86Presentation
> Internal error: Could not resolve keysym XF86Database
> Internal error: Could not resolve keysym XF86Voicemail
> Internal error: Could not resolve keysym XF86Addressbook
> Internal error: Could not resolve keysym XF86DisplayToggle
> Internal error: Could not resolve keysym XF86SpellCheck
> Internal error: Could not resolve keysym XF86ContextMenu
> Internal error: Could not resolve keysym XF86MediaRepeat
> Internal error: Could not resolve keysym XF8610ChannelsUp
> Internal error: Could not resolve keysym XF8610ChannelsDown
> Internal error: Could not resolve keysym XF86Images
> Internal error: Could not resolve keysym XF86NotificationCenter
> Internal error: Could not resolve keysym XF86PickupPhone
> Internal error: Could not resolve keysym XF86HangupPhone
> Internal error: Could not resolve keysym XF86Fn
> Internal error: Could not resolve keysym XF86Fn_Esc
> Internal error: Could not resolve keysym XF86FnRightShift
> Internal error: Could not resolve keysym XF86Numeric0
> Internal error: Could not resolve keysym XF86Numeric1
> Internal error: Could not resolve keysym XF86Numeric2
> Internal error: Could not resolve keysym XF86Numeric3
> Internal error: Could not resolve keysym XF86Numeric4
> Internal error: Could not resolve keysym XF86Numeric5
> Internal error: Could not resolve keysym XF86Numeric6
> Internal error: Could not resolve keysym XF86Numeric7
> Internal error: Could not resolve keysym XF86Numeric8
> Internal error: Could not resolve keysym XF86Numeric9
> Internal error: Could not resolve keysym XF86NumericStar
> Internal error: Could not resolve keysym XF86NumericPound
> Internal error: Could not resolve keysym XF86NumericA
> Internal error: Could not resolve keysym XF86NumericB
> Internal error: Could not resolve keysym XF86NumericC
> Internal error: Could not resolve keysym XF86NumericD
> Internal error: Could not resolve keysym XF86CameraFocus
> Internal error: Could not resolve keysym XF86WPSButton
> Internal error: Could not resolve keysym XF86CameraZoomIn
> Internal error: Could not resolve keysym XF86CameraZoomOut
> Internal error: Could not resolve keysym XF86CameraUp
> Internal error: Could not resolve keysym XF86CameraDown
> Internal error: Could not resolve keysym XF86CameraLeft
> Internal error: Could not resolve keysym XF86CameraRight
> Internal error: Could not resolve keysym XF86AttendantOn
> Internal error: Could not resolve keysym XF86AttendantOff
> Internal error: Could not resolve keysym XF86AttendantToggle
> Internal error: Could not resolve keysym XF86LightsToggle
> Internal error: Could not resolve keysym XF86ALSToggle
> Internal error: Could not resolve keysym XF86Buttonconfig
> Internal error: Could not resolve keysym XF86Taskmanager
> Internal error: Could not resolve keysym XF86Journal
> Internal error: Could not resolve keysym XF86ControlPanel
> Internal error: Could not resolve keysym XF86AppSelect
> Internal error: Could not resolve keysym XF86Screensaver
> Internal error: Could not resolve keysym XF86VoiceCommand
> Internal error: Could not resolve keysym XF86Assistant
> Internal error: Could not resolve keysym XF86BrightnessMin
> Internal error: Could not resolve keysym XF86BrightnessMax
> Internal error: Could not resolve keysym XF86KbdInputAssistPrev
> Internal error: Could not resolve keysym XF86KbdInputAssistNext
> Internal error: Could not resolve keysym XF86KbdInputAssistPrevgroup
> Internal error: Could not resolve keysym XF86KbdInputAssistNextgroup
> Internal error: Could not resolve keysym XF86KbdInputAssistAccept
> Internal error: Could not resolve keysym XF86KbdInputAssistCancel
> Internal error: Could not resolve keysym XF86RightUp
> Internal error: Could not resolve keysym XF86RightDown
> Internal error: Could not resolve keysym XF86LeftUp
> Internal error: Could not resolve keysym XF86LeftDown
> Internal error: Could not resolve keysym XF86RootMenu
> Internal error: Could not resolve keysym XF86MediaTopMenu
> Internal error: Could not resolve keysym XF86Numeric11
> Internal error: Could not resolve keysym XF86Numeric12
> Internal error: Could not resolve keysym XF86AudioDesc
> Internal error: Could not resolve keysym XF863DMode
> Internal error: Could not resolve keysym XF86NextFavorite
> Internal error: Could not resolve keysym XF86StopRecord
> Internal error: Could not resolve keysym XF86PauseRecord
> Internal error: Could not resolve keysym XF86VOD
> Internal error: Could not resolve keysym XF86Unmute
> Internal error: Could not resolve keysym XF86FastReverse
> Internal error: Could not resolve keysym XF86SlowReverse
> Internal error: Could not resolve keysym XF86Data
> Internal error: Could not resolve keysym XF86OnScreenKeyboard
> Internal error: Could not resolve keysym XF86PrivacyScreenToggle
> Internal error: Could not resolve keysym XF86SelectiveScreenshot
> Internal error: Could not resolve keysym XF86Macro1
> Internal error: Could not resolve keysym XF86Macro2
> Internal error: Could not resolve keysym XF86Macro3
> Internal error: Could not resolve keysym XF86Macro4
> Internal error: Could not resolve keysym XF86Macro5
> Internal error: Could not resolve keysym XF86Macro6
> Internal error: Could not resolve keysym XF86Macro7
> Internal error: Could not resolve keysym XF86Macro8
> Internal error: Could not resolve keysym XF86Macro9
> Internal error: Could not resolve keysym XF86Macro10
> Internal error: Could not resolve keysym XF86Macro11
> Internal error: Could not resolve keysym XF86Macro12
> Internal error: Could not resolve keysym XF86Macro13
> Internal error: Could not resolve keysym XF86Macro14
> Internal error: Could not resolve keysym XF86Macro15
> Internal error: Could not resolve keysym XF86Macro16
> Internal error: Could not resolve keysym XF86Macro17
> Internal error: Could not resolve keysym XF86Macro18
> Internal error: Could not resolve keysym XF86Macro19
> Internal error: Could not resolve keysym XF86Macro20
> Internal error: Could not resolve keysym XF86Macro21
> Internal error: Could not resolve keysym XF86Macro22
> Internal error: Could not resolve keysym XF86Macro23
> Internal error: Could not resolve keysym XF86Macro24
> Internal error: Could not resolve keysym XF86Macro25
> Internal error: Could not resolve keysym XF86Macro26
> Internal error: Could not resolve keysym XF86Macro27
> Internal error: Could not resolve keysym XF86Macro28
> Internal error: Could not resolve keysym XF86Macro29
> Internal error: Could not resolve keysym XF86Macro30
> Internal error: Could not resolve keysym XF86MacroRecordStart
> Internal error: Could not resolve keysym XF86MacroRecordStop
> Internal error: Could not resolve keysym XF86MacroPresetCycle
> Internal error: Could not resolve keysym XF86MacroPreset1
> Internal error: Could not resolve keysym XF86MacroPreset2
> Internal error: Could not resolve keysym XF86MacroPreset3
> Internal error: Could not resolve keysym XF86KbdLcdMenu1
> Internal error: Could not resolve keysym XF86KbdLcdMenu2
> Internal error: Could not resolve keysym XF86KbdLcdMenu3
> Internal error: Could not resolve keysym XF86KbdLcdMenu4
> Internal error: Could not resolve keysym XF86KbdLcdMenu5
Errors from xkbcomp are not fatal to the X server
```
I tried to update/bump xorgproto, xkbcomp, xkeyboard-config, libX11, but those do not go away.
Any idea?
Thanks.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo @ 2021-07-09 13:43 ` ericonr 2021-07-09 13:50 ` dkwo ` (22 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: ericonr @ 2021-07-09 13:43 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 218 bytes --] New comment by ericonr on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-877199544 Comment: What's your environment (WM/.xinit file)? Have you checked `xbps-pkgdb -a`? ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo 2021-07-09 13:43 ` ericonr @ 2021-07-09 13:50 ` dkwo 2021-07-09 13:55 ` dkwo ` (21 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-09 13:50 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 1370 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-877204200 Comment: I use dwm ``` $ cat .xinitrc #!/bin/bash monitor=DP-2-2 laptop=eDP-1 if $(xrandr | grep -q "$monitor connected"); then xrandr --output $laptop --off --output $monitor --auto --dpi 163 else xrandr --auto --dpi 216 # xinput set-prop 11 311 1 fi # HDTV: xrandr --output eDP1 --off --output HDMI2 --auto export GDK_DPI_SCALE=2 export LIBVA_DRIVER_NAME=iHD clipdel -d ".*" (export CM_IGNORE_WINDOW=KeePassXC; clipmenud &) # glibc ~/.dropbox-dist/dropboxd > ~/Projects/dropbox.log 2>&1 & numlockx redshift -l 60:17 -t 5700:3600 -g 0.8 -m randr -v > ~/Projects/redshift.log 2>&1 & # bg 45:10 up 60:17 ~/Projects/suckless/dwm_status.sh & feh --bg-max ~/Pictures/bkground/* # xautolock -time 30 -locker slockcustom & # xss-lock slockcustom & # xset s 1200 xset r rate 300 60 xrdb -merge ~/.Xresources if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then eval `dbus-launch --sh-syntax --exit-with-session` fi #-- ensure XDG_Runtime_dir is set unset XDG_RUNTIME_DIR export XDG_RUNTIME_DIR=$(mktemp -d /tmp/$(id -u)-runtime-dir.XXX) /usr/bin/pipewire & exec dwm 2> ~/Projects/dwm.log ``` The only `ERROR`s in `xbps-pkgdb -a` come from `mtime mismatch`. ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo 2021-07-09 13:43 ` ericonr 2021-07-09 13:50 ` dkwo @ 2021-07-09 13:55 ` dkwo 2021-07-09 14:19 ` biopsin ` (20 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-09 13:55 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 9125 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-877207892 Comment: This is my `dwm-config.h`, not sure if it's relevant. ``` /* See LICENSE file for copyright and license details. */ /* appearance */ static const unsigned int borderpx = 1; /* border pixel of windows */ static const unsigned int snap = 32; /* snap pixel */ static const int showbar = 1; /* 0 means no bar */ static const int topbar = 1; /* 0 means bottom bar */ // static const char *fonts[] = { "Terminus (TTF):size=12" }; // arch static const char *fonts[] = { "xos4 Terminus:size=12" }; static const char *fonts[] = { "Terminus:size=12" }; static const char dmenufont[] = "Terminus:size=12"; static const char col_gray1[] = "#222222"; static const char col_gray2[] = "#444444"; static const char col_gray3[] = "#bbbbbb"; static const char col_gray4[] = "#eeeeee"; static const char col_cyan[] = "#005577"; static const char *colors[][3] = { /* fg bg border */ [SchemeNorm] = { col_gray3, col_gray1, col_gray2 }, [SchemeSel] = { col_gray4, col_cyan, col_cyan }, }; /* tagging */ static const char *tags[] = { "1", "2", "3", "4", "5", "6", "7", "8", "9" }; static const Rule rules[] = { /* xprop(1): * WM_CLASS(STRING) = instance, class * WM_NAME(STRING) = title */ /* class instance title tags mask isfloating monitor */ { "Gimp", NULL, NULL, 0, 1, -1 }, { "Firefox", NULL, NULL, 0, 0, -1 }, }; /* layout(s) */ static const float mfact = 0.5; /* factor of master area size [0.05..0.95] */ static const int nmaster = 1; /* number of clients in master area */ static const int resizehints = 1; /* 1 means respect size hints in tiled resizals */ static const Layout layouts[] = { /* symbol arrange function */ { "[]=", tile }, /* first entry is default */ { "><>", NULL }, /* no layout function means floating behavior */ { "[M]", monocle }, }; /* key definitions */ #define XF86MonBrightnessDown 0x1008ff03 #define XF86MonBrightnessUp 0x1008ff02 #define XF86AudioMute 0x1008ff12 #define XF86AudioLowerVolume 0x1008ff11 #define XF86AudioRaiseVolume 0x1008ff13 #define MODKEY Mod1Mask #define TAGKEYS(KEY,TAG) \ { MODKEY, KEY, view, {.ui = 1 << TAG} }, \ { MODKEY|ControlMask, KEY, toggleview, {.ui = 1 << TAG} }, \ { MODKEY|ShiftMask, KEY, tag, {.ui = 1 << TAG} }, \ { MODKEY|ControlMask|ShiftMask, KEY, toggletag, {.ui = 1 << TAG} }, /* helper for spawning shell commands in the pre dwm-5.0 fashion */ #define SHCMD(cmd) { .v = (const char*[]){ "/bin/sh", "-c", cmd, NULL } } /* commands */ static char dmenumon[2] = "0"; /* component of dmenucmd, manipulated in spawn() */ static const char *dmenucmd[] = { "dmenu_run", "-m", dmenumon, "-fn", dmenufont, "-nb", col_gray1, "-nf", col_gray3, "-sb", col_cyan, "-sf", col_gray4, NULL }; static const char *termcmd[] = { "st", "-e", "tmux", NULL }; static const char *urlcmd[] = { "clipmenu-url", NULL }; static const char *clipcmd[] = { "clipmenu", "-i", "-fn", dmenufont, NULL }; /* will need symlink to brightness in /usr/local/bin */ static const char *cmdbrightnessup[] = { "doas", "/usr/bin/brightness", "up", NULL }; static const char *cmdbrightnessdown[] = { "doas", "/usr/bin/brightness", "down", NULL }; static const char *cmdsoundup[] = { "amixer", "-q", "sset", "Master", "5%+", NULL }; static const char *cmdsounddown[] = { "amixer", "-q", "sset", "Master", "5%-", NULL }; static const char *cmdsoundtoggle[] = { "amixer", "-q", "sset", "Master", "toggle", NULL }; static const char *cmdrshift[] = { "show-clipboard", NULL }; static const char *cmdlock[] = { "slockcustom", NULL }; static const char *firefox[] = { "firefox", NULL }; static const char *thunderbird[] = { "thunderbird", NULL }; /* static const char *nautilus[] = { "nautilus", NULL }; */ static const char *screenlock[] = { "slockcustom", NULL}; static Key keys[] = { /* modifier key function argument */ { MODKEY, XK_Insert, spawn, SHCMD("maim -s ~/Pictures/$(date +%s).png") }, { MODKEY, XK_Home, spawn, {.v = clipcmd } }, { MODKEY, XK_o, spawn, {.v = urlcmd } }, { MODKEY, XK_p, spawn, {.v = dmenucmd } }, { MODKEY|ShiftMask, XK_Return, spawn, {.v = termcmd } }, { MODKEY, XK_f, spawn, {.v = firefox } }, /* { MODKEY, XK_n, spawn, {.v = nautilus } }, */ { MODKEY, XK_t, spawn, {.v = thunderbird } }, { MODKEY, XK_l, spawn, {.v = screenlock } }, { MODKEY, XK_b, togglebar, {0} }, { 0, XK_Print, spawn, {.v = cmdrshift } }, { MODKEY, XK_F12, spawn, {.v = cmdlock } }, { 0, XF86MonBrightnessDown, spawn, {.v = cmdbrightnessdown } }, { 0, XF86MonBrightnessUp, spawn, {.v = cmdbrightnessup } }, { 0, XF86AudioMute, spawn, {.v = cmdsoundtoggle } }, { 0, XF86AudioRaiseVolume, spawn, {.v = cmdsoundup } }, { 0, XF86AudioLowerVolume, spawn, {.v = cmdsounddown } }, { MODKEY, XK_j, focusstack, {.i = +1 } }, { MODKEY, XK_k, focusstack, {.i = -1 } }, { MODKEY, XK_i, incnmaster, {.i = +1 } }, { MODKEY, XK_d, incnmaster, {.i = -1 } }, { MODKEY, XK_h, setmfact, {.f = -0.05} }, { MODKEY, XK_z, setmfact, {.f = +0.05} }, { MODKEY, XK_Return, zoom, {0} }, { MODKEY, XK_Tab, view, {0} }, { MODKEY|ShiftMask, XK_c, killclient, {0} }, { MODKEY, XK_y, setlayout, {.v = &layouts[0]} }, { MODKEY|ShiftMask, XK_g, setlayout, {.v = &layouts[1]} }, { MODKEY, XK_m, setlayout, {.v = &layouts[2]} }, { MODKEY, XK_space, setlayout, {0} }, { MODKEY|ShiftMask, XK_space, togglefloating, {0} }, { MODKEY, XK_0, view, {.ui = ~0 } }, { MODKEY|ShiftMask, XK_0, tag, {.ui = ~0 } }, { MODKEY, XK_comma, focusmon, {.i = -1 } }, { MODKEY, XK_period, focusmon, {.i = +1 } }, { MODKEY|ShiftMask, XK_comma, tagmon, {.i = -1 } }, { MODKEY|ShiftMask, XK_period, tagmon, {.i = +1 } }, TAGKEYS( XK_1, 0) TAGKEYS( XK_2, 1) TAGKEYS( XK_3, 2) TAGKEYS( XK_4, 3) TAGKEYS( XK_5, 4) TAGKEYS( XK_6, 5) TAGKEYS( XK_7, 6) TAGKEYS( XK_8, 7) TAGKEYS( XK_9, 8) { MODKEY|ShiftMask, XK_q, quit, {0} }, }; /* button definitions */ /* click can be ClkLtSymbol, ClkStatusText, ClkWinTitle, ClkClientWin, or ClkRootWin */ static Button buttons[] = { /* click event mask button function argument */ { ClkLtSymbol, 0, Button1, setlayout, {0} }, { ClkLtSymbol, 0, Button3, setlayout, {.v = &layouts[2]} }, { ClkWinTitle, 0, Button2, zoom, {0} }, { ClkStatusText, 0, Button2, spawn, {.v = termcmd } }, { ClkClientWin, MODKEY, Button1, movemouse, {0} }, { ClkClientWin, MODKEY, Button2, togglefloating, {0} }, { ClkClientWin, MODKEY, Button3, resizemouse, {0} }, { ClkTagBar, 0, Button1, view, {0} }, { ClkTagBar, 0, Button3, toggleview, {0} }, { ClkTagBar, MODKEY, Button1, tag, {0} }, { ClkTagBar, MODKEY, Button3, toggletag, {0} }, }; ``` ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (2 preceding siblings ...) 2021-07-09 13:55 ` dkwo @ 2021-07-09 14:19 ` biopsin 2021-07-09 14:22 ` biopsin ` (19 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: biopsin @ 2021-07-09 14:19 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 281 bytes --] New comment by biopsin on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-877223825 Comment: I have the same output, tried bumping xorgproto and rebuilt xkbcomp, but to no avail. This issue happens before a WM is loaded via startx ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (3 preceding siblings ...) 2021-07-09 14:19 ` biopsin @ 2021-07-09 14:22 ` biopsin 2021-07-09 14:51 ` leahneukirchen ` (18 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: biopsin @ 2021-07-09 14:22 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 1037 bytes --] New comment by biopsin on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-877223825 Comment: I have the same output, tried bumping xorgproto and rebuilt xkbcomp, but to no avail. This issue happens before a WM is loaded via startx ``` [ -d /etc/X11/xinit/xinitrc.d ] && \ for f in /etc/X11/xinit/xinitrc.d/*; do [ -x "$f" ] && . "$f"; done && unset f # Setup XDG_RUNTIME_DIR & pam_env mkdir -p /tmp/${USER}-runtime && chmod -R 0700 /tmp/${USER}-runtime export XDG_RUNTIME_DIR=/tmp/${USER}-runtime # Start user dbus-daemon pidof -s dbus-daemon || export $(dbus-launch) # Run userx services runsvdir -P "$HOME/.local/service" & # Enable clipmenu /usr/local/bin/clipmenud & # Set random bg /usr/local/bin/rngbd & # Dim screen 40% /usr/bin/xcalib -co 40 -gc 1.25 /usr/share/xcalib/gamma_1_0.icc # Compositor xcompmgr -cCb # Start wm exec pekwm --config "$HOME/.config/pekwm/config" #exec pekwm --log-file /tmp/pekwm_issue.log --log-level trace ``` ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (4 preceding siblings ...) 2021-07-09 14:22 ` biopsin @ 2021-07-09 14:51 ` leahneukirchen 2021-07-09 15:14 ` biopsin ` (17 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: leahneukirchen @ 2021-07-09 14:51 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 469 bytes --] New comment by leahneukirchen on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-877245360 Comment: Apparently this is harmless: https://bugzilla.redhat.com/show_bug.cgi?id=1615700 Culprit I think is ``` /usr/share/X11/xkb/keycodes/evdev: <I256> = 256; // #define KEY_MICMUTE 248 /usr/share/X11/xkb/symbols/inet: key <I256> { [ XF86AudioMicMute ] }; // KEY_MICMUTE ``` ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (5 preceding siblings ...) 2021-07-09 14:51 ` leahneukirchen @ 2021-07-09 15:14 ` biopsin 2021-07-10 7:16 ` travankor ` (16 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: biopsin @ 2021-07-09 15:14 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 232 bytes --] New comment by biopsin on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-877260613 Comment: They are, but before I had like 2-3 of them not 137 which is bit to much harmelss spam ;) ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (6 preceding siblings ...) 2021-07-09 15:14 ` biopsin @ 2021-07-10 7:16 ` travankor 2021-07-10 11:47 ` biopsin ` (15 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: travankor @ 2021-07-10 7:16 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 208 bytes --] New comment by travankor on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-877585651 Comment: I see this output on Wayland compositors from Xwayland as well. ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (7 preceding siblings ...) 2021-07-10 7:16 ` travankor @ 2021-07-10 11:47 ` biopsin 2021-07-16 20:18 ` dkwo ` (14 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: biopsin @ 2021-07-10 11:47 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 267 bytes --] New comment by biopsin on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-877624842 Comment: Maybe expand on previous patch https://github.com/void-linux/void-packages/commit/5773cf4c5fea354a0625fa468f1babbfe674b7a0 ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (8 preceding siblings ...) 2021-07-10 11:47 ` biopsin @ 2021-07-16 20:18 ` dkwo 2021-07-16 20:19 ` ericonr ` (13 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-16 20:18 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 341 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-881695034 Comment: On the other hand, https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/commit/c8cfca25ab2ed65013448f7502bae933c66390ae seems to imply this can be avoided (at least the long list of `could not resolve`). ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (9 preceding siblings ...) 2021-07-16 20:18 ` dkwo @ 2021-07-16 20:19 ` ericonr 2021-07-17 8:38 ` biopsin ` (12 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: ericonr @ 2021-07-16 20:19 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 289 bytes --] New comment by ericonr on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-881695886 Comment: > libX11 just hasn't yet been rebuilt against the protocol Maybe we should rebuild libX11 ever so often? Could you test if that fixes anything? ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (10 preceding siblings ...) 2021-07-16 20:19 ` ericonr @ 2021-07-17 8:38 ` biopsin 2021-07-17 10:25 ` dkwo ` (11 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: biopsin @ 2021-07-17 8:38 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 347 bytes --] New comment by biopsin on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-881858188 Comment: Just did the following building: xorgproto to 2021.4.99.2 -> libX11 -> xkbcomp to 1.4.5 -> xkeyboard-config -> libX11 but the list still prints however "> internal error" is replaced with "> warning" .. ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (11 preceding siblings ...) 2021-07-17 8:38 ` biopsin @ 2021-07-17 10:25 ` dkwo 2021-07-17 19:48 ` ericonr ` (10 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-17 10:25 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 424 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-881873088 Comment: I think I had the same experience before ``` libxkbcommon: revbump for libX11 xkeyboard-config: revbump for libX11 xorgproto: update libX11: update xkbcomp: update to 1.4.5 ``` Is there anything else that should be revbumped? or maybe the order is crucial? ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (12 preceding siblings ...) 2021-07-17 10:25 ` dkwo @ 2021-07-17 19:48 ` ericonr 2021-07-18 10:21 ` dkwo ` (9 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: ericonr @ 2021-07-17 19:48 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 249 bytes --] New comment by ericonr on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-881951055 Comment: @dkwo if you revbump all of them and then `xbulk <all of them>`, it should figure out the correct order ;) ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (13 preceding siblings ...) 2021-07-17 19:48 ` ericonr @ 2021-07-18 10:21 ` dkwo 2021-07-18 21:21 ` ericonr ` (8 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-18 10:21 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 202 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-882033996 Comment: @ericonr Sure, but do you see anything missing from that list? ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (14 preceding siblings ...) 2021-07-18 10:21 ` dkwo @ 2021-07-18 21:21 ` ericonr 2021-07-19 7:50 ` dkwo ` (7 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: ericonr @ 2021-07-18 21:21 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 174 bytes --] New comment by ericonr on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-882118348 Comment: Not that I can think of, sorry. ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (15 preceding siblings ...) 2021-07-18 21:21 ` ericonr @ 2021-07-19 7:50 ` dkwo 2021-07-19 11:32 ` ericonr ` (6 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-19 7:50 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 510 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-882325228 Comment: Funny enough, if I `xbulk libxkbcommon xkeyboard-config xorgproto libX11 xkbcomp `and `xi libxkbcommon xkeyboard-config libX11 xkbcomp` (xorgproto was not installed before) the high keycode goes away, and I'm left with just all the warnings ``` The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Could not resolve keysym XF86BrightnessAuto ``` ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (16 preceding siblings ...) 2021-07-19 7:50 ` dkwo @ 2021-07-19 11:32 ` ericonr 2021-07-19 12:13 ` dkwo ` (5 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: ericonr @ 2021-07-19 11:32 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 176 bytes --] New comment by ericonr on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-882475422 Comment: I'm okay with that being PR'd :P ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (17 preceding siblings ...) 2021-07-19 11:32 ` ericonr @ 2021-07-19 12:13 ` dkwo 2021-07-19 14:46 ` dkwo ` (4 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-19 12:13 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 185 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-882498969 Comment: Done. I'm still partially puzzled, though :) ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (18 preceding siblings ...) 2021-07-19 12:13 ` dkwo @ 2021-07-19 14:46 ` dkwo 2021-07-19 15:59 ` ericonr ` (3 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-19 14:46 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 301 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-882608828 Comment: Btw, if I want to rebuild all packages in a PR, will `./xbps-src update-bulk` do that, while figuring out the correct order, as `xbulk <name all packages>` does? ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (19 preceding siblings ...) 2021-07-19 14:46 ` dkwo @ 2021-07-19 15:59 ` ericonr 2021-07-24 16:06 ` dkwo ` (2 subsequent siblings) 23 siblings, 0 replies; 25+ messages in thread From: ericonr @ 2021-07-19 15:59 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 240 bytes --] New comment by ericonr on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-882665415 Comment: It should, though in a less efficient manner, maybe. The build pipeline will get it right tho. ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (20 preceding siblings ...) 2021-07-19 15:59 ` ericonr @ 2021-07-24 16:06 ` dkwo 2021-07-27 9:41 ` dkwo 2021-07-28 13:11 ` [ISSUE] [CLOSED] " dkwo 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-24 16:06 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 321 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-886073209 Comment: If I downgrade `xkeyboard-config` to 2.32, the warnings go away. Do you see anything suspicious here https://cgit.freedesktop.org/xkeyboard-config/log/ or in the way we build it? ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (21 preceding siblings ...) 2021-07-24 16:06 ` dkwo @ 2021-07-27 9:41 ` dkwo 2021-07-28 13:11 ` [ISSUE] [CLOSED] " dkwo 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-27 9:41 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 157 bytes --] New comment by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870#issuecomment-887367924 Comment: Finally solved :) ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [ISSUE] [CLOSED] xkbcomp errors 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo ` (22 preceding siblings ...) 2021-07-27 9:41 ` dkwo @ 2021-07-28 13:11 ` dkwo 23 siblings, 0 replies; 25+ messages in thread From: dkwo @ 2021-07-28 13:11 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 10016 bytes --] Closed issue by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/31870 Description: ``` $ xuname Void 5.12.14_1 x86_64-musl GenuineIntel uptodate rrnFFFFFFF $ xbps-query -p pkgver xkbcomp xkbcomp-1.4.2_1 ``` Xorg logs: ``` X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 Build Operating System: Linux Void Current Operating System: Linux ajax 5.12.14_1 #1 SMP 1625102948 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-5.12.14_1 root=UUID=802049d2-8957-4735-8ddb-53d09b9bfcd8 ro loglevel=4 rd.luks.name=809df427-d7d5-408c-a195-3be6e86813 33=cryptroot root=/dev/mapper/cryptroot rd.luks.options=discard Build Date: 18 April 2021 03:55:47AM Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Fri Jul 9 09:46:34 2021 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Unsupported high keycode 256 for name <I256> ignored > X11 cannot support keycodes above 255. > This warning only shows for the first high keycode. > Internal error: Could not resolve keysym XF86BrightnessAuto > Internal error: Could not resolve keysym XF86DisplayOff > Internal error: Could not resolve keysym XF86Info > Internal error: Could not resolve keysym XF86AspectRatio > Internal error: Could not resolve keysym XF86DVD > Internal error: Could not resolve keysym XF86Audio > Internal error: Could not resolve keysym XF86ChannelUp > Internal error: Could not resolve keysym XF86ChannelDown > Internal error: Could not resolve keysym XF86Break > Internal error: Could not resolve keysym XF86VideoPhone > Internal error: Could not resolve keysym XF86ZoomReset > Internal error: Could not resolve keysym XF86Editor > Internal error: Could not resolve keysym XF86GraphicsEditor > Internal error: Could not resolve keysym XF86Presentation > Internal error: Could not resolve keysym XF86Database > Internal error: Could not resolve keysym XF86Voicemail > Internal error: Could not resolve keysym XF86Addressbook > Internal error: Could not resolve keysym XF86DisplayToggle > Internal error: Could not resolve keysym XF86SpellCheck > Internal error: Could not resolve keysym XF86ContextMenu > Internal error: Could not resolve keysym XF86MediaRepeat > Internal error: Could not resolve keysym XF8610ChannelsUp > Internal error: Could not resolve keysym XF8610ChannelsDown > Internal error: Could not resolve keysym XF86Images > Internal error: Could not resolve keysym XF86NotificationCenter > Internal error: Could not resolve keysym XF86PickupPhone > Internal error: Could not resolve keysym XF86HangupPhone > Internal error: Could not resolve keysym XF86Fn > Internal error: Could not resolve keysym XF86Fn_Esc > Internal error: Could not resolve keysym XF86FnRightShift > Internal error: Could not resolve keysym XF86Numeric0 > Internal error: Could not resolve keysym XF86Numeric1 > Internal error: Could not resolve keysym XF86Numeric2 > Internal error: Could not resolve keysym XF86Numeric3 > Internal error: Could not resolve keysym XF86Numeric4 > Internal error: Could not resolve keysym XF86Numeric5 > Internal error: Could not resolve keysym XF86Numeric6 > Internal error: Could not resolve keysym XF86Numeric7 > Internal error: Could not resolve keysym XF86Numeric8 > Internal error: Could not resolve keysym XF86Numeric9 > Internal error: Could not resolve keysym XF86NumericStar > Internal error: Could not resolve keysym XF86NumericPound > Internal error: Could not resolve keysym XF86NumericA > Internal error: Could not resolve keysym XF86NumericB > Internal error: Could not resolve keysym XF86NumericC > Internal error: Could not resolve keysym XF86NumericD > Internal error: Could not resolve keysym XF86CameraFocus > Internal error: Could not resolve keysym XF86WPSButton > Internal error: Could not resolve keysym XF86CameraZoomIn > Internal error: Could not resolve keysym XF86CameraZoomOut > Internal error: Could not resolve keysym XF86CameraUp > Internal error: Could not resolve keysym XF86CameraDown > Internal error: Could not resolve keysym XF86CameraLeft > Internal error: Could not resolve keysym XF86CameraRight > Internal error: Could not resolve keysym XF86AttendantOn > Internal error: Could not resolve keysym XF86AttendantOff > Internal error: Could not resolve keysym XF86AttendantToggle > Internal error: Could not resolve keysym XF86LightsToggle > Internal error: Could not resolve keysym XF86ALSToggle > Internal error: Could not resolve keysym XF86Buttonconfig > Internal error: Could not resolve keysym XF86Taskmanager > Internal error: Could not resolve keysym XF86Journal > Internal error: Could not resolve keysym XF86ControlPanel > Internal error: Could not resolve keysym XF86AppSelect > Internal error: Could not resolve keysym XF86Screensaver > Internal error: Could not resolve keysym XF86VoiceCommand > Internal error: Could not resolve keysym XF86Assistant > Internal error: Could not resolve keysym XF86BrightnessMin > Internal error: Could not resolve keysym XF86BrightnessMax > Internal error: Could not resolve keysym XF86KbdInputAssistPrev > Internal error: Could not resolve keysym XF86KbdInputAssistNext > Internal error: Could not resolve keysym XF86KbdInputAssistPrevgroup > Internal error: Could not resolve keysym XF86KbdInputAssistNextgroup > Internal error: Could not resolve keysym XF86KbdInputAssistAccept > Internal error: Could not resolve keysym XF86KbdInputAssistCancel > Internal error: Could not resolve keysym XF86RightUp > Internal error: Could not resolve keysym XF86RightDown > Internal error: Could not resolve keysym XF86LeftUp > Internal error: Could not resolve keysym XF86LeftDown > Internal error: Could not resolve keysym XF86RootMenu > Internal error: Could not resolve keysym XF86MediaTopMenu > Internal error: Could not resolve keysym XF86Numeric11 > Internal error: Could not resolve keysym XF86Numeric12 > Internal error: Could not resolve keysym XF86AudioDesc > Internal error: Could not resolve keysym XF863DMode > Internal error: Could not resolve keysym XF86NextFavorite > Internal error: Could not resolve keysym XF86StopRecord > Internal error: Could not resolve keysym XF86PauseRecord > Internal error: Could not resolve keysym XF86VOD > Internal error: Could not resolve keysym XF86Unmute > Internal error: Could not resolve keysym XF86FastReverse > Internal error: Could not resolve keysym XF86SlowReverse > Internal error: Could not resolve keysym XF86Data > Internal error: Could not resolve keysym XF86OnScreenKeyboard > Internal error: Could not resolve keysym XF86PrivacyScreenToggle > Internal error: Could not resolve keysym XF86SelectiveScreenshot > Internal error: Could not resolve keysym XF86Macro1 > Internal error: Could not resolve keysym XF86Macro2 > Internal error: Could not resolve keysym XF86Macro3 > Internal error: Could not resolve keysym XF86Macro4 > Internal error: Could not resolve keysym XF86Macro5 > Internal error: Could not resolve keysym XF86Macro6 > Internal error: Could not resolve keysym XF86Macro7 > Internal error: Could not resolve keysym XF86Macro8 > Internal error: Could not resolve keysym XF86Macro9 > Internal error: Could not resolve keysym XF86Macro10 > Internal error: Could not resolve keysym XF86Macro11 > Internal error: Could not resolve keysym XF86Macro12 > Internal error: Could not resolve keysym XF86Macro13 > Internal error: Could not resolve keysym XF86Macro14 > Internal error: Could not resolve keysym XF86Macro15 > Internal error: Could not resolve keysym XF86Macro16 > Internal error: Could not resolve keysym XF86Macro17 > Internal error: Could not resolve keysym XF86Macro18 > Internal error: Could not resolve keysym XF86Macro19 > Internal error: Could not resolve keysym XF86Macro20 > Internal error: Could not resolve keysym XF86Macro21 > Internal error: Could not resolve keysym XF86Macro22 > Internal error: Could not resolve keysym XF86Macro23 > Internal error: Could not resolve keysym XF86Macro24 > Internal error: Could not resolve keysym XF86Macro25 > Internal error: Could not resolve keysym XF86Macro26 > Internal error: Could not resolve keysym XF86Macro27 > Internal error: Could not resolve keysym XF86Macro28 > Internal error: Could not resolve keysym XF86Macro29 > Internal error: Could not resolve keysym XF86Macro30 > Internal error: Could not resolve keysym XF86MacroRecordStart > Internal error: Could not resolve keysym XF86MacroRecordStop > Internal error: Could not resolve keysym XF86MacroPresetCycle > Internal error: Could not resolve keysym XF86MacroPreset1 > Internal error: Could not resolve keysym XF86MacroPreset2 > Internal error: Could not resolve keysym XF86MacroPreset3 > Internal error: Could not resolve keysym XF86KbdLcdMenu1 > Internal error: Could not resolve keysym XF86KbdLcdMenu2 > Internal error: Could not resolve keysym XF86KbdLcdMenu3 > Internal error: Could not resolve keysym XF86KbdLcdMenu4 > Internal error: Could not resolve keysym XF86KbdLcdMenu5 Errors from xkbcomp are not fatal to the X server ``` I tried to update/bump xorgproto, xkbcomp, xkeyboard-config, libX11, but those do not go away. Any idea? Thanks. ^ permalink raw reply [flat|nested] 25+ messages in thread
end of thread, other threads:[~2021-07-28 13:11 UTC | newest] Thread overview: 25+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-07-09 12:26 [ISSUE] xkbcomp errors dkwo 2021-07-09 13:43 ` ericonr 2021-07-09 13:50 ` dkwo 2021-07-09 13:55 ` dkwo 2021-07-09 14:19 ` biopsin 2021-07-09 14:22 ` biopsin 2021-07-09 14:51 ` leahneukirchen 2021-07-09 15:14 ` biopsin 2021-07-10 7:16 ` travankor 2021-07-10 11:47 ` biopsin 2021-07-16 20:18 ` dkwo 2021-07-16 20:19 ` ericonr 2021-07-17 8:38 ` biopsin 2021-07-17 10:25 ` dkwo 2021-07-17 19:48 ` ericonr 2021-07-18 10:21 ` dkwo 2021-07-18 21:21 ` ericonr 2021-07-19 7:50 ` dkwo 2021-07-19 11:32 ` ericonr 2021-07-19 12:13 ` dkwo 2021-07-19 14:46 ` dkwo 2021-07-19 15:59 ` ericonr 2021-07-24 16:06 ` dkwo 2021-07-27 9:41 ` dkwo 2021-07-28 13:11 ` [ISSUE] [CLOSED] " dkwo
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).