[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



Hi Michel,

Le mer., juil. 6 2022 at 10:09:31 +0200, Michel Dänzer <michel.daenzer@mailbox.org> a écrit :
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?

paul@frank:~$ lsof /tmp/.X11-unix/X*
COMMAND     PID USER   FD   TYPE             DEVICE SIZE/OFF  NODE NAME
gnome-she 5382 paul 55u unix 0x00000000f9c78a52 0t0 55362 /tmp/.X11-unix/X1 type=STREAM (LISTEN) Xwayland 16890 paul 5u unix 0x000000004a4eebcd 0t0 55360 /tmp/.X11-unix/X0 type=STREAM (LISTEN)


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.

Output of "strace" here: https://paste.debian.net/1246358/

I don't see it even trying to open the socket…

-Paul


Reply to: