José Expósito 722e464bff test: Xwayland doesn't start when another X server is running ...

When running the xserver:xwayland / XTS test in an environment where
an X server is running for :0, Xwayland fails to start with error:

    (EE)
    Fatal server error:
    (EE) Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.
    (EE)

And the `timeout` command fails instead of waiting for Weston to
initialize.

Add the `-displayfd` parameter to Xwayland to avoid this issue.

The `-displayfd` parameter lets Xwayland pick an unused display number,
avoiding the start up error when an X server is already active for :0,
the default display number.

Suggested-by: Michel Dänzer <mdaenzer@redhat.com>
Signed-off-by: José Expósito <jexposit@redhat.com>

2023-09-27 11:59:53 +02:00

..

build-travis-osx.sh

Remove autotools support

2021-10-27 13:15:40 +03:00

run-piglit.sh

Revert "ci: Work around broken python UTF8 handling in the CI docker image"

2018-12-17 17:52:39 +01:00

xephyr-glamor-gles2-piglit.sh

meson: add glamor gles2 tests

2022-12-01 08:41:57 +00:00

xephyr-glamor-piglit.sh

test: Exclude two XTS xsetfontpath tests

2022-09-02 14:49:08 +02:00

xinit-piglit-session.sh

test: Exclude two XTS xsetfontpath tests

2022-09-02 14:49:08 +02:00

xvfb-piglit.sh

ci: Ignore builds for branches aimed at other CI services

2018-03-21 09:35:38 -04:00

xwayland-piglit.sh

test: Xwayland doesn't start when another X server is running

2023-09-27 11:59:53 +02:00