Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0

[Michel Dänzer <michel.daenzer@mailbox.org>]

On 2022-07-05 21:09, Paul Cercueil wrote:
> Le mar., juil. 5 2022 at 20:46:44 +0200, Michel Dänzer <michel.daenzer@mailbox.org> a écrit :
> 
> The message in french from gsd-xsettings is "Cannot open display:"

Thanks for the clarification (I thought "affichage" meant "file" :).

It seems likely then that gnome-shell's failure to initialize GDK is due to failing to open the X11 display as well.


>> What value does $DISPLAY contain after logging in?
>
> [...]
> 
> $DISPLAY is :0 after logging in. Using DISPLAY=:1 does not seem to change anything.

Let's take a step back.

The journal should contain a line like

 gnome-shell[<PID>]: Using public X11 display :0, (using :1 for managed services)

The display number before "for managed services" is what gnome-shell itself and gsd-xsettings use for connecting to Xwayland.

Does the corresponding socket exist under /tmp/.X11-unix, e.g. /tmp/.X11-unix/X1 ? If yes, what does lsof say for it?


Assuming the socket exists and Xwayland is listening on it, maybe try running gsd-xsettings with that display number under strace, to see if that gives any clues about the failure.


-- 
Earthling Michel Dänzer            |                  https://redhat.com
Libre software enthusiast          |         Mesa and Xwayland developer