mutter fails to determine the right display when an X servers was started with `displayfd`
Affected version
- Fedora 33
- mutter from master (tip at commit 98ef6d0d)
- Wayland
Bug summary
When an Xserver is started with -displayfd
, no lock file (/tmp/.Xn-lock) is created.
Mutter looks for the lock file to determine which X11 display to use with Xwayland, and will fail to get the display right whenever there is a running X server started with -displayfd
(like e.g. xvfb-run
does).
Steps to reproduce
- Start Xephyr with displayfd:
$ Xephyr -displayfd 1 &
- Run gnome-shell nested 1:
$ dbus-run-session -- jhbuild run gnome-shell --wayland --nested
- From
gnome-shell
, launch an xterm
What happened
xterm
is started in the Xephyr window instead of gnome-shell
What did you expect to happen
xterm
is started in gnome-shell
Relevant logs, screenshots, screencasts etc.
N/A
-
We use “nested” here for convenience, the same happens in a real session as well!
↩