On some machines chrome refuses to start with
[6536:6536:1005/054746.213927:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

This chrome is not intended to be used for more than running testsuites, so I
believe we can live without the extra security chrome sandbox would have
offered us.

in order not to leak processes on Ctrl+C

Software just to in install a test runner

Instead of what this software was supposed to be before

enable X11 backend, xrandr, xfixes xcomposite and xdamage

(includeing webpdemux that's needed for webkit)

0.16.1, 0.19.0 and 0.22.0

This is next ESR version, but for now it still have to be used
explicitly.

see https://bugs.freedesktop.org/show_bug.cgi?id=105287