[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





Le mer., juil. 6 2022 at 18:56:47 +0200, Michel Dänzer <michel.daenzer@mailbox.org> a écrit :
On 2022-07-06 18:00, Paul Cercueil wrote:
Le mer., juil. 6 2022 at 16:44:46 +0200, Michel Dänzer <michel.daenzer@mailbox.org> a écrit :
 On 2022-07-06 14:33, Paul Cercueil wrote:

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

I think Olivier Fourdan figured it out on IRC #gnome-shell: All your symptoms can be reproduced if the environment variable GDK_BACKEND=wayland is set for gnome-shell & gsd-xsettings. It's likely that this is in your environment for some reason (it's not set by default by anything I know of).

 That was it!

I set GDK_BACKEND=wayland in my ~/.bash_profile in order to get Firefox to use Wayland.

FWIW, I use MOZ_ENABLE_WAYLAND=1 for this.

Yes, I do set MOZ_ENABLE_WAYLAND=1 as well. It used to also require GDK_BACKEND=wayland, but it is not the case anymore, apparently.

 Removing GDK_BACKEND=wayland from the environment fixes it.

Great.


I've created https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2496 & https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/302 to make mutter & gnome-settings-daemon robust against this.


Assuming it was the same cause for Harlan, I suggest reassigning this bug to libmutter-10-0.

Understood. Thanks again.

Cheers,
-Paul


Reply to: