Control: affects -1 + xwayland-run On Sat, 13 Dec 2025 at 16:09:06 +0100, Rene Engelhard wrote:
$ xwfb-run -e /dev/stderr true; echo $?
...
0 with xkb-data 2.44 and $ xwfb-run -e /dev/stderr true; echo $? Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE)
...
1 with xkb-data 2.46
Looks like the xkb-data regression affects both xvfb-run and xwfb-run equally, so xwfb-run is not a useful workaround in this case.
The updated xkb-data is also causing GTK programs to crash (#1122805) which is probably another effect of the same root cause.
[xwfb-run] unfortunately fails with --auto-servernum
Yes, it isn't 100% command-line compatible with xvfb-run (from the --help, it seems like it expects -a to take a boolean argument). But -a is documented to be a no-op for xwfb-run anyway (I assume it's on by default in that implementation).
smcv