[SOLVED] gdm-x-session floods journal w/ "Could not resolve keysym"

Cbhihe · 2021-09-23 14:53:41

The journal on one of my boxes (Dell XPS15-9560) is flooded with warning from gdm-x-session per this partial pastebin dump... obtained with

journalctl -b | grep -e "gdm-x-session"

See warnings from line 396 on.
Full boot log pastebin is available at here.

Boot was with discrete GPU Nvidia GTX 1050 completely disabled.

I don't know where and when that started and I've tried to understand the issue for the past day and a half. (Prior I had not looked at my systemd journal during a week or so ... , and across four-ish minor kernel updates). My current belief is I had no such issue prior to kernel v5.14 but the truth is I'm not sure since apart from one "stutter" in the boot sequence I have no adverse consequence when that box becomes alive, except for the fact that my journal is flooded.

My setup is:
Linux HOSTNAME 5.14.6-arch1-1 #1 SMP PREEMPT Sat, 18 Sep 2021 16:19:35 +0000 x86_64 GNU/Linux running:
- xorg-xwayland 21.1.2-1 (xorg)
- xorg-xkbcomp 1.4.5-1 (xorg-apps xorg)
- xorg-server 1.20.13-2 (xorg)
- gdm 40.1-2 (gnome)
- libgdm 40.1-2
- libx11 1.7.2-1

My boot option (in `/etc/default/grub`) are:

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet mds=full acpi_rev_override=1 acpi_osi=Linux resume=/dev/disk/by-uuid/...

The full pastebin dump shows I have other warnings at boot, namely:

 wmi_bus wmi_bus-PNP0C14:03: WQBC data block query control method not found
 ...
 ACPI Warning: \_SB.IETM._TRT: Return Package has no elements (empty) (20210604/nsprepkg-94)
 ...
 psmouse serio1: synaptics: Unable to query device: -5
 ...
 nmbd[895]: [2021/09/23 11:10:21.910296,  0] ../../source3/nmbd/nmbd.c:902(main)
 nmbd[895]:   nmbd version 4.15.0 started.
 nmbd[895]:   Copyright Andrew Tridgell and the Samba Team 1992-2021 
 nmbd[895]: [2021/09/23 11:10:21.912781,  0] ../../lib/util/become_daemon.c:150(daemon_status) 
 nmbd[895]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
 nmbd[895]: [2021/09/23 11:10:21.912923,  0] ../../source3/nmbd/nmbd_subnetdb.c:252(create_subnets)
 nmbd[895]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
 ...
 gnome-session-binary[1218]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist.
 ...

.. and little more I could notice.
The info imparted on `nmbd` are attributable to a badly configured `samba` setup I think. That's next on my list of TODOs :-(

Would be grateful for help in particular about the warnings reported by the "XKEYBOARD keymap compiler (xkbcomp)":

 > Warning:          Could not resolve keysym XF86...

Last edited by Cbhihe (2021-09-27 18:21:05)

seth · 2021-09-23 15:47:39

https://bbs.archlinux.org/viewtopic.php … 7#p1982347

Cbhihe · 2021-09-23 16:39:08

Tx, I followed the trail...

> Warning: Unsupported high keycode 372 for name <I372> ignored
> X11 cannot support keycodes above 255.
> This warning only shows for the first high keycode.
Errors from xkbcomp are not fatal to the X server

...
and got to Peter Hutterer's answer:

that's fine. we've started adding high keycodes to xkeyboard-config because we can finally handle them on wayland. but the same maps are used under X where we can't - hence the warning. It's just a warning, no functional changes (those keycodes were never available anyway).

That covers the why. Pfff ! As for getting rid of those warnings, my .bash_profile has

   #if [ -z "$DISPLAY" ] && [ -n "$XDG_VTNR" ] && [ "$XDG_VTNR" -eq 1 ] ; then
   #     exec startx
   #fi

because I do not want to autostart X at login, so that I cannot make it into an

    if...; then
        exec startx  > /dev/null 2>&1
    fi

so how can I apply the redirection to send those warning into neverland ?...

Last edited by Cbhihe (2021-09-23 19:51:49)

seth · 2021-09-23 19:42:29

afaics GDM launches Xorg from some binary wrapper - you probably can't impat that.
But /usr/bin/Xorg is actually a wrapper script and you could redirect the output/log there ("-logfile filename", GDM moves it to the journal - I *assume* using this parameter)

Cbhihe · 2021-09-23 20:20:40

Yes, when gdm launches Xorg, everything becomes a little more complicated, as both /usr/lib/Xorg and its wrapper are binary executables.
I tried modifying /usr/bin/Xorg, but:
- option -logfile is only available for launch of Xorg by root, and
- option -quiet is ineffectual... apparently (by checking boot journal after change + reboot)
So, probably a dead end.
Thanks for pointing me toward the "unsupported high keycodes" explanation.

seth · 2021-09-23 21:02:36

According to http://who-t.blogspot.com/2014/03/viewi … alctl.html (the most lazy, thus dated, google result) GDM uses /dev/null as logfile and redirects stdout/err, so if it calls the wrapper script "grep -v"ing stdout/err for the undesired token migt do.

Cbhihe · 2021-09-27 18:20:09

Yes !! The modified /usr/bin/Xorg below does change things. Namely I have 4630+ fewer junk lines in my systemd boot journal.

> cat /usr/bin/Xorg
#!/bin/sh
# Execute Xorg.wrap if it exists otherwise execute Xorg directly.
# This allows distros to put the suid wrapper in a separate package.
basedir="/usr/lib"
if [ -x "$basedir"/Xorg.wrap ]; then
	exec "$basedir"/Xorg.wrap "$@" 2> >(grep -v "Could not resolve keysym")
else
	exec "$basedir"/Xorg "$@" 2> >(grep -v "Could not resolve keysym")
fi

Tx @Seth for the suggestion. Solved.

Arch Linux

#1 2021-09-23 14:53:41

[SOLVED] gdm-x-session floods journal w/ "Could not resolve keysym"

#2 2021-09-23 15:47:39

Re: [SOLVED] gdm-x-session floods journal w/ "Could not resolve keysym"

#3 2021-09-23 16:39:08

Re: [SOLVED] gdm-x-session floods journal w/ "Could not resolve keysym"

#4 2021-09-23 19:42:29

Re: [SOLVED] gdm-x-session floods journal w/ "Could not resolve keysym"

#5 2021-09-23 20:20:40

Re: [SOLVED] gdm-x-session floods journal w/ "Could not resolve keysym"

#6 2021-09-23 21:02:36

Re: [SOLVED] gdm-x-session floods journal w/ "Could not resolve keysym"

#7 2021-09-27 18:20:09

Re: [SOLVED] gdm-x-session floods journal w/ "Could not resolve keysym"

Board footer