Commits on Source (6)
-
With EI support wired to XTEST, and oeffis being enabled unconditionally means that Xwayland will always go through the XDG portal for XTEST when supported. While this the intended behavior for the general use case of Xwayland running rootless on a desktop compositor, that breaks when Xwayland is running on a nested compositor, because the portal is for the entire session and not limited to the nested Wayland compositor. Xwayland itself, as a regular Wayland client, has no way to tell that it is running on a nested compositor. So to keep backward compatibility with existing (and also common) use cases such as nested compositors, best is to disable support for the XDG portal by default, and add a new command line option "-enable-ei-portal" for the Wayland compositors (who spawn Xwayland rootless) to explicitly enable support for the input emulation XDG portal in Xwayland. A Wayland compositor running nested should not use that command line option with Xwayland. Signed-off-by:
Olivier Fourdan <ofourdan@redhat.com> Reviewed-by:
Joshua Ashton <joshua@froggi.es> Fixes: a1333342 - xwayland: Add XTEST support using EIS Closes: #1586 See-also: https://gitlab.gnome.org/GNOME/mutter/-/issues/3047
-
If we fail to setup EI, give up on using EI for XTEST and restore the default XTEST handlers. This happens when neither the portal nor the socket backends are usable. This does not affect the portal operation though, if the user choose not to allow a particular client, Xwayland would continue to use EI. Signed-off-by:
Olivier Fourdan <ofourdan@redhat.com> Reviewed-by:
Joshua Ashton <joshua@froggi.es>
-
Michel Dänzer authored
This should be plenty even on CI, no need to wait for a whole minute if something goes wrong.
-
Michel Dänzer authored
This script runs with -e, so if the timeout command returns a non-0 exit status (meaning the while loop timed out), the script exits immediately as well. This would leave weston running in the background, which resulted in meson waiting for weston to terminate until hitting meson's own timeout. Instead, explicitly kill weston whenever the shell exits. This results in meson recording the test as failed immediately. As a bonus, we can drop the special handling around run-piglit.sh. v2: * Use trap (José Expósito) v3: * Explicitly use bash, and document a bashism we rely on (Olivier Fourdan)
-
Michel Dänzer authored
If waiting for weston to start times out. This should make it easier to diagnose issues.
-
Michel Dänzer authored
No point starting weston and waiting for it to start up in that case.
Showing
- hw/xwayland/man/Xwayland.man 9 additions, 0 deletionshw/xwayland/man/Xwayland.man
- hw/xwayland/meson.build 1 addition, 0 deletionshw/xwayland/meson.build
- hw/xwayland/xwayland-screen.c 7 additions, 0 deletionshw/xwayland/xwayland-screen.c
- hw/xwayland/xwayland-screen.h 1 addition, 0 deletionshw/xwayland/xwayland-screen.h
- hw/xwayland/xwayland-xtest.c 7 additions, 2 deletionshw/xwayland/xwayland-xtest.c
- hw/xwayland/xwayland.c 6 additions, 0 deletionshw/xwayland/xwayland.c
- test/scripts/xwayland-piglit.sh 23 additions, 8 deletionstest/scripts/xwayland-piglit.sh