This probably an issue with opensuse160-vk-1 worker. I'm opening a bug entry to track these and see if it happens on other worker. I should mail the helpdesk about it early next week. ==================================================================================================== Step 5/5: Running command DISPLAY=:1 xterm -geometry 90x30 -e ${SCRIPTSDIR}/bitbake-extra-tests; exit $(cat bbextratests-exitcode) (1780540505.6: 0.0) ==================================================================================================== Poky - The Yocto Project testing distribution Running '. ./init-build-env; DISPLAY=:1 xterm -geometry 90x30 -e ${SCRIPTSDIR}/bitbake-extra-tests; exit $(cat bbextratests-exitcode)' with output to /srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build/command-5-cmds.log in /srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build xterm: Xt error: Can't open display: :1 cat: bbextratests-exitcode: No such file or directory
oe-selftest-fedora opensuse160-vk-1 master completed at 2026-06-04 02:35:06+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3818/steps/22/logs/stdio oe-selftest-fedora opensuse160-vk-1 master completed at 2026-06-05 04:00:53+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3826/steps/22/logs/stdio
oe-selftest-fedora opensuse160-vk-1 wrynose completed at 2026-06-05 14:02:55+00:00 https://autobuilder.yoctoproject.org/valkyrie/?#/builders/48/builds/3830
We'll track this to see if the qemu upgrade helps. We suspect that qemu has been taking out the X server somehow...
Michael confirmed vnc was stopped on this worker.
oe-selftest-fedora opensuse160-vk-1 master completed at 2026-06-22 02:33:59+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3947/steps/22/logs/stdio
oe-selftest-fedora opensuse160-vk-1 mathieu/master-next completed at 2026-07-04 07:58:31+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4037/steps/22/logs/stdio
oe-selftest-fedora opensuse160-vk-1 master completed at 2026-07-07 03:52:58+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4060/steps/22/logs/stdio
oe-selftest-fedora opensuse160-vk-1 master completed at 2026-07-18 02:34:12+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4131/steps/22/logs/stdio oe-selftest-fedora opensuse160-vk-1 mathieu/master-next&mathieu/master-next-tests completed at 2026-07-18 06:40:09+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4132/steps/22/logs/stdio
oe-selftest-fedora opensuse160-vk-1 stable/2.18-nut&stable/wrynose-nut completed at 2026-07-04 16:40:07+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4039/steps/22/logs/stdio
oe-selftest-fedora opensuse160-vk-1 wrynose completed at 2026-07-21 18:14:51+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4158
oe-selftest-fedora opensuse160-vk-1 master completed at 2026-07-23 02:37:44+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4172/steps/22/logs/stdio
I checked on the system and vnc wasn't running. I was able to start it without issue. I don't think it must have been restarted after maintenance?
I emailed helpdesk to seek assistance
We found a rouge screensaver package which was on vk-1 but not vk-2, we've removed that and believe the issue to be resolved.
oe-selftest-fedora opensuse160-vk-1 mathieu/master-next completed at 2026-08-07 06:53:29+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4308/steps/24/logs/stdio oe-selftest-fedora opensuse160-vk-1 mathieu/master-next completed at 2026-08-07 08:34:14+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4309/steps/24/logs/stdio
oe-selftest-fedora opensuse160-vk-1 master&mathieu/master-next completed at 2026-08-07 13:10:16+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4313/steps/24/logs/stdio oe-selftest-fedora opensuse160-vk-1 master-next completed at 2026-08-09 10:58:29+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4329/steps/24/logs/stdio
After recent updates the problem has returned. Starting from a shell works fine however systemd puts this in the log. source: usage: source filename [arguments] dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Rather than continuing to troubleshoot I'm going to replace vnc with a headless Xwayland display on :1.
I believe the issue came back again, still the same worker. oe-selftest-fedora opensuse160-vk-1 master completed at 2026-10-01 17:03:21+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4780/steps/24/logs/stdio oe-selftest-fedora opensuse160-vk-1 master-next completed at 2026-09-30 12:15:08+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4768/steps/24/logs/stdio
oe-selftest-fedora opensuse160-vk-1 master completed at 2026-10-03 02:39:50+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4802/steps/24/logs/stdio oe-selftest-fedora opensuse160-vk-1 master-next&master completed at 2026-10-03 11:57:13+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4805/steps/24/logs/stdio oe-selftest-fedora opensuse160-vk-1 master completed at 2026-10-05 02:45:27+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4815/steps/24/logs/stdio
Reopening.
I've removed Xvnc from the OpenSUSE workers and replaced it with Xwayland framebuffer. This should permanently resolve the issue.