Solved Wrong mode for /tmp (X would not start; SDDM reappeared after attempting to log in)

[Cath O'Deray]

Part of the following command (for /tmp, not for /var/tmp) was necessary after upgrading from 13.2-RELEASE to 13.2-RELEASE-p4 to 14.0-RC3 then 14.0-RC4:

# chmod 1777 /tmp && chmod 1777 /var/tmp

From <https://termbin.com/t1q7x>:

…
[  1492.232] (EE) Error compiling keymap (server-1) executing '"/usr/local/bin/xkbcomp" -w 1 "-R/usr/local/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "/tmp/server-1.xkm"'
[  1492.232] (EE) XKB: Couldn't compile keymap
[  1492.232] (EE) XKB: Failed to load keymap. Loading default keymap instead.
[  1492.352] (EE) Error compiling keymap (server-1) executing '"/usr/local/bin/xkbcomp" -w 1 "-R/usr/local/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "/tmp/server-1.xkm"'
[  1492.352] (EE) XKB: Couldn't compile keymap
[  1492.352] XKB: Failed to compile keymap
[  1492.352] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
[  1492.352] (EE)
Fatal server error:
[  1492.352] (EE) Failed to activate virtual core keyboard: 2(EE)
…

Attached: a screenshot of the wrong mode.

I temporarily activated two of the earliest boot environments that preceded the upgrades, found the same wrong mode.

Realistically, I can't describe it as a bug, because (sorry) I was too lazy to check whether X was usable before the upgrades.

A possible clue to the origin of the wrongness, my naming of the virtual machine, which preceded the upgrades:

… crashed during or after the second freebsd-update for 13.2

Solved, but someone might find it of interest.