Bug#1122855: xvfb-run broken after todays updates?
Hi, Am 13.12.25 um 15:40 schrieb Simon McVittie: On Sat, 13 Dec 2025 at 12:06:29 +0100, Rene Engelhard wrote: root@frodo:~# xvfb-run --auto-servernum true; echo $? 1 For what it's worth, this is working as expected for me and exiting 0 (in up-to-date unstable on amd64, either on a laptop or in a podman container) so perhaps there is some other factor. On a system where this doesn't work, running as "xvfb-run -e /dev/stderr --auto-servernum true" might produce useful information (or not). For historical reasons Xvfb's stderr is sent to /dev/null by default. For updated/future packages, I wonder whether it's time to be preferring the utilities from the xwayland-run package (wlheadless-run for native Wayland apps, or xwfb-run for X11 apps) as a wrapper for regression tests that reflects how users of our most common desktop environments will increasingly be using the app. Which unfortunately fails with --auto-servernum: $ xwfb-run -e /dev/stderr --auto-servernum true usage: xwfb-run [-h] [-a AUTO_SERVERNUM] [-c COMPOSITOR] [-d AUTO_DISPLAY] [-e ERROR_FILE] [-f AUTH_FILE] [-n SERVER_NUM] [-l] [-p XAUTH_PROTO] [-s SERVER_ARGS] [-w WAIT] [-z COMPOSITOR_ARGS] [command ...] Run an X11 client in a dedicated Xwayland server on a Wayland compositor headless. positional arguments: command The program to run and arguments. options: -h, --help show this help message and exit -a, --auto-servernum AUTO_SERVERNUM Unused, kept for backward compatibility only. -c, --compositor COMPOSITOR Use the compositor class implementation. -d, --auto-display AUTO_DISPLAY Unused, kept for backward compatibility only. -e, --error-file ERROR_FILE File used to store xauth and X server errors. -f, --auth-file AUTH_FILE File used to store auth cookie. -n, --server-num SERVER_NUM Xserver number to use. -l, --listen-tcp Enable TCP port listening in the X server. -p, --xauth-proto XAUTH_PROTO Xauthority protocol name to use. -s, --server-args SERVER_ARGS Arguments to pass to the X server. -w, --wait WAIT Delay in seconds to wait for the X server to start before running COMMAND. -z, --compositor-args COMPOSITOR_ARGS Arguments to pass to the Wayland compositor. so is not exactly argument-compatible... But running it here gives: $ xwfb-run -e /dev/stderr true; echo $? Date: 2025-12-13 CET [16:05:00.741] weston 14.0.2 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: 14.0.2 [16:05:00.741] Command line: weston --no-config --backend headless --socket wayland-485968 [16:05:00.741] OS: Linux, 6.12.57+deb13-amd64, #1 SMP PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05), x86_64 [16:05:00.741] Flight recorder: enabled [16:05:00.741] Starting with no config file. [16:05:00.741] Output repaint window is 7 ms maximum. [16:05:00.741] Loading module '/usr/lib/x86_64-linux-gnu/libweston-14/headless-backend.so' [16:05:00.745] Registered plugin API 'weston_windowed_output_api_headless_v2' of size 16 [16:05:00.745] Color manager: no-op protocol support: no [16:05:00.745] Output 'headless' attempts EOTF mode SDR and colorimetry mode default. [16:05:00.745] Output 'headless' using color profile: stock sRGB color profile [16:05:00.745] Output 'headless' enabled with head(s) headless [16:05:00.745] Compositor capabilities: arbitrary surface rotation: no screen capture uses y-flip: no cursor planes: no arbitrary resolutions: no view mask clipping: no explicit sync: no color operations: no presentation clock: CLOCK_MONOTONIC_RAW, id 4 presentation clock resolution: 0.1 s [16:05:00.745] Loading module '/usr/lib/x86_64-linux-gnu/weston/desktop-shell.so' [16:05:00.745] launching '/usr/libexec/weston-keyboard' [16:05:00.746] launching '/usr/libexec/weston-desktop-shell' could not load cursor 'dnd-copy' could not load cursor 'dnd-none' could not load cursor 'dnd-copy' could not load cursor 'dnd-none' Xwayland glamor: GBM Wayland interfaces not available Failed to initialize glamor, falling back to sw The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Could not resolve keysym XF86RefreshRateToggle > Warning: Could not resolve keysym XF86Accessibility > Warning: Could not resolve keysym XF86DoNotDisturb Errors from xkbcomp are not fatal to the X server [16:05:01.780] caught signal 15 [16:05:01.780] no-op renderer SHM seed: 2 0 with xkb-data 2.44 and rene@frodo:~/LibreOffice/git/master$ xwfb-run true; echo $? Xwayland failed to start! 1 rene@frod
Bug#1122855: xvfb-run broken after todays updates?
reassign 1122855 xvfb-run broken afte xkb-data upgrade found 1122855 2.46-1 affects 1122855 xvfb thanks Hi, Am 13.12.25 um 15:40 schrieb Simon McVittie: On a system where this doesn't work, running as "xvfb-run -e /dev/stderr --auto-servernum true" might produce useful information (or not). For historical reasons Xvfb's stderr is sent to /dev/null by default. Thanks for the hint. It does: $ xvfb-run -e /dev/stderr --auto-servernum true XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) /usr/bin/xvfb-run: 91: kill: No such process which would match xvfb-run brokenGet:52 http://deb.debian.org/debian unstable/main amd64 xkb-data all 2.46-1 [830 kB] being updated, too... And indeed: root@frodo:~# xvfb-run --auto-servernum true; echo $? 1 root@frodo:~# dpkg -i /home/rene/xkb-data_2.44-1_all.deb dpkg: warning: downgrading xkb-data (2.46-1) to (2.44-1) (Reading database ... 229339 files and directories currently installed.) Preparing to unpack .../rene/xkb-data_2.44-1_all.deb ... Unpacking xkb-data (2.44-1) over (2.46-1) ... Setting up xkb-data (2.44-1) ... Processing triggers for man-db (2.13.1-1) ... root@frodo:~# xvfb-run --auto-servernum true; echo $? 0 The question is what changed... Regards, Rene
Bug#1122855: xvfb-run broken after todays updates?
On Sat, 13 Dec 2025 at 12:06:29 +0100, Rene Engelhard wrote: root@frodo:~# xvfb-run --auto-servernum true; echo $? 1 For what it's worth, this is working as expected for me and exiting 0 (in up-to-date unstable on amd64, either on a laptop or in a podman container) so perhaps there is some other factor. On a system where this doesn't work, running as "xvfb-run -e /dev/stderr --auto-servernum true" might produce useful information (or not). For historical reasons Xvfb's stderr is sent to /dev/null by default. For updated/future packages, I wonder whether it's time to be preferring the utilities from the xwayland-run package (wlheadless-run for native Wayland apps, or xwfb-run for X11 apps) as a wrapper for regression tests that reflects how users of our most common desktop environments will increasingly be using the app. smcv
Bug#1122855: xvfb-run broken after todays updates?
Package: xvfb Version: 2:21.1.21-1 Severity: serious Justifictation: makes other packages FTBFS Hi, I iam not exactly sure who is at fault, reassign as appropriate. Sorry, I don't have much more information. If you need some extra ones i can try stuff, though. root@frodo:~# xvfb-run --auto-servernum true; echo $? 0 Here it works. (That command is used in LibreOffices configure script to check whether xvfb-run works) Now upgrade: root@frodo:~# apt upgrade The following packages were automatically installed and are no longer required: libdw-dev libelf-dev libstdc++-14-dev libunwind-dev llvm-19 llvm-19-runtime Use 'apt autoremove' to remove them. Upgrading: cron gir1.2-edatabook-1.2 libc6 libebook-1.2-21t64 libevdev2 locales cron-daemon-commongir1.2-edataserver-1.2libc6-dev libebook-contacts-1.2-4t64 libfribidi-dev locales-all dconf-gsettings-backend git-debpush libc6-i386 libebook-contacts1.2-devlibfribidi0 python3-lz4 dconf-service libasound2-data libcamel-1.2-64t64 libebook1.2-dev libmime-types-perl python3-markdown evolution-data-server-common libasound2t64 libcamel1.2-dev libedata-book-1.2-27t64 libpq-dev sqv gir1.2-camel-1.2 libc-bin libdconf-dev libedata-book1.2-devlibpq5 tzdata gir1.2-ebackend-1.2 libc-dev-bin libdconf1 libedataserver-1.2-27t64libtdb1 xkb-data gir1.2-ebook-1.2 libc-gconv-modules-extra libebackend-1.2-11t64 libedataserver1.2-dev libvisual-0.4-0 gir1.2-ebookcontacts-1.2 libc-l10n libebackend1.2-dev libevdev-devlibyuv0 Not upgrading: graphviz libselinux1 Summary: Upgrading: 52, Installing: 0, Removing: 0, Not Upgrading: 2 Download size: 31.4 MB Space needed: 3944 kB / 4179 MB available Continue? [Y/n] Get:1 http://deb.debian.org/debian unstable/main amd64 libc-dev-bin amd64 2.42-6 [60.7 kB] Get:2 http://deb.debian.org/debian unstable/main amd64 libc6-dev amd64 2.42-6 [2090 kB] Get:3 http://deb.debian.org/debian unstable/main amd64 libc6-i386 amd64 2.42-6 [2554 kB] Get:4 http://deb.debian.org/debian unstable/main amd64 libc-gconv-modules-extra amd64 2.42-6 [1123 kB] Get:5 http://deb.debian.org/debian unstable/main amd64 libc6 amd64 2.42-6 [1889 kB] Get:6 http://deb.debian.org/debian unstable/main amd64 libc-bin amd64 2.42-6 [674 kB] Get:7 http://deb.debian.org/debian unstable/main amd64 cron amd64 3.0pl1-202 [88.1 kB] Get:8 http://deb.debian.org/debian unstable/main amd64 sqv amd64 1.3.0-5 [648 kB] Get:9 http://deb.debian.org/debian unstable/main amd64 tzdata all 2025c-1 [263 kB] Get:10 http://deb.debian.org/debian unstable/main amd64 cron-daemon-common all 3.0pl1-202 [18.2 kB] Get:11 http://deb.debian.org/debian unstable/main amd64 libc-l10n all 2.42-6 [749 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 locales all 2.42-6 [3926 kB] Get:13 http://deb.debian.org/debian unstable/main amd64 libdconf-dev amd64 0.49.0-4 [6768 B] Get:14 http://deb.debian.org/debian unstable/main amd64 dconf-gsettings-backend amd64 0.49.0-4 [30.0 kB] Get:15 http://deb.debian.org/debian unstable/main amd64 dconf-service amd64 0.49.0-4 [34.0 kB] Get:16 http://deb.debian.org/debian unstable/main amd64 libdconf1 amd64 0.49.0-4 [43.9 kB] Get:17 http://deb.debian.org/debian unstable/main amd64 evolution-data-server-common all 3.56.2-7 [1445 kB] Get:18 http://deb.debian.org/debian unstable/main amd64 libebook1.2-dev amd64 3.56.2-7 [42.4 kB] Get:19 http://deb.debian.org/debian unstable/main amd64 libedata-book1.2-dev amd64 3.56.2-7 [85.8 kB] Get:20 http://deb.debian.org/debian unstable/main amd64 libebackend1.2-dev amd64 3.56.2-7 [67.5 kB] Get:21 http://deb.debian.org/debian unstable/main amd64 libebook-contacts1.2-dev amd64 3.56.2-7 [55.4 kB] Get:22 http://deb.debian.org/debian unstable/main amd64 libedataserver1.2-dev amd64 3.56.2-7 [192 kB] Get:23 http://deb.debian.org/debian unstable/main amd64 libcamel1.2-dev amd64 3.56.2-7 [265 kB] Get:24 http://deb.debian.org/debian unstable/main amd64 libcamel-1.2-64t64 amd64 3.56.2-7 [472 kB] Get:25 http://deb.debian.org/debian unstable/main amd64 libebook-contacts-1.2-4t64 amd64 3.56.2-7 [70.0 kB] Get:26 http://deb.debian.org/debian unstable/main amd64 gir1.2-edatabook-1.2 amd64 3.56.2-7 [27.3 kB] Get:27 http://deb.debian.org/debian unstable/main amd64 gir1.2-ebackend-1.2 amd64 3.56.2-7 [22.1 kB] Get:28 http://deb.debian.org/debian unstable/main amd64 gir1.2-ebook-1.2 amd64 3.56.2-7 [15.9 kB] Get:29 http://deb.debian.org/debian unstable/main amd64 gir1.2-ebookcontacts-1.2 amd64 3.56.2-7 [22.4 kB] Get:30 http://deb.debian.org/debian unstable/main amd64 gir1.2-edataserver-1.2 amd64 3.56.2-7 [45
