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

[Paul Cercueil <paul@crapouillou.net>]

Le mar., juil. 5 2022 at 20:46:44 +0200, Michel Dänzer 
<michel.daenzer@mailbox.org> a écrit :
> On 2022-07-05 18:28, Paul Cercueil wrote:
> >  Le mar., juil. 5 2022 at 15:51:08 +0200, Michel Dänzer 
> > <michel.daenzer@mailbox.org> a écrit :
> > >  On 2022-07-05 14:48, Paul Cercueil wrote:
> > > >   Is there a way I can provide more information?
> > >
> > >  Come to think of it, capturing the journal output after trying to 
> > > start an X11 client might be interesting:
> > >
> > >   journalctl --user -b0
> >
> >  This was giving me zero results so I ran 'journalctl -b0' and some 
> > things happened when trying to run 'xterm':
> >
> >  [...]
> >
> >  juil. 05 17:24:03 frank gsd-xsettings[3959]: Impossible d’ouvrir 
> > l’affichage :
> >  juil. 05 17:24:03 frank systemd[2111]: 
> > org.gnome.SettingsDaemon.XSettings.service: Main process exited, 
> > code=exited, status=1/FAILURE
> >  juil. 05 17:24:03 frank systemd[2111]: 
> > org.gnome.SettingsDaemon.XSettings.service: Failed with result 
> > 'exit-code'.
> >  juil. 05 17:24:03 frank systemd[2111]: Failed to start GNOME 
> > XSettings service.
> >  juil. 05 17:24:03 frank gnome-shell[2215]: Window manager warning: 
> > L’initialisation de GDK a échoué
> >  juil. 05 17:24:03 frank gnome-shell[2215]: Failed to initialize X11 
> > display: Failed to initialize GDK
>
> Looks like the problem is either that gsd-xsettings fails to start, 
> or that gnome-shell fails to initialize GDK.
>
> On the former, does
>
>  journalctl --user-unit=org.gnome.SettingsDaemon.XSettings.service -b0
>
>
> or
>
>  systemctl --user status org.gnome.SettingsDaemon.XSettings.service
>
> provide more information about the failure?

journalctl gives me this:

juil. 05 19:58:04 frank systemd[2014]: Starting GNOME XSettings 
service...
juil. 05 19:58:05 frank systemd[2014]: Started GNOME XSettings service.
juil. 05 19:58:40 frank systemd[2014]: Dependency failed for GNOME 
XSettings service.
juil. 05 19:58:40 frank systemd[2014]: 
org.gnome.SettingsDaemon.XSettings.service: Job 
org.gnome.SettingsDaemon.XSettings.service/start failed with result 
'dependency'.
juil. 05 19:58:55 frank systemd[2014]: Starting GNOME XSettings 
service...
juil. 05 19:58:55 frank gsd-xsettings[4159]: Impossible d’ouvrir 
l’affichage :
juil. 05 19:58:55 frank systemd[2014]: 
org.gnome.SettingsDaemon.XSettings.service: Main process exited, 
code=exited, status=1/FAILURE
juil. 05 19:58:55 frank systemd[2014]: 
org.gnome.SettingsDaemon.XSettings.service: Failed with result 
'exit-code'.
juil. 05 19:58:55 frank systemd[2014]: Failed to start GNOME XSettings 
service.
juil. 05 19:58:55 frank systemd[2014]: 
org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, 
restart counter is at 1.

The message in french from gsd-xsettings is "Cannot open display:"


> > >  Also, does setting DISPLAY=:1 (or whatever is the default number + 
> > > 1) work better?
> >
> >  It does not seem to change anything, running 'DISPLAY=:1 xterm' 
> > just hangs (doesn't open a window), the only difference I can see is 
> > that no Xwayland process is started.
>
> What value does $DISPLAY contain after logging in?
>
> What if you try DISPLAY=:1 once Xwayland is running? If that works, 
> maybe try
>
>  DISPLAY=:1 /usr/libexec/gsd-xsettings -v
>
> to see if that gives more information about the failure.

$DISPLAY is :0 after logging in. Using DISPLAY=:1 does not seem to 
change anything.

I tried:

DISPLAY=:0 /usr/libexec/gsd-xsettings -v
DISPLAY=:1 /usr/libexec/gsd-xsettings -v

Both print the exact same error message as above, and nothing else.

I tried as well:

/usr/libexec/gsd-xsettings -v --display=:0
/usr/libexec/gsd-xsettings -v --display=:1

I get the same error message, but this time it did print back the 
display on the error message: "Cannot open display: :1"

> On 2022-07-05 18:26, Paul Cercueil wrote:
> >  Le mar., juil. 5 2022 at 15:31:25 +0200, Michel Dänzer 
> > <michel.daenzer@mailbox.org> a écrit :
> > >  On 2022-07-05 14:48, Paul Cercueil wrote:
> >
> > > >   I end up having to work under Windows, ugh.
> > >
> > >  Surely you can use a GNOME on Xorg session in the worst case.
> >
> >  Is that still a thing? I can't select Gnome on X11 anymore since 
> > the last few releases of Gnome. GDM simply doesn't give me the 
> > option.
>
> That's unexpected, I can still choose "GNOME on Xorg" on my machines.
>
> Do you have xserver-xorg installed?

Ha, good point. I re-installed the "xserver-xorg" package and now I do 
have the "GNOME on Xorg" option back.

Cheers,
-Paul