Open dajhorn opened 1 year ago
Yeah, the only way currently to run Browservice with WSLg is to remove the symlink or run Browservice with command line option --use-dedicated-xvfb=NO
(causing the browser to run in the desktop X session). I currently don't have good ideas on how to fix this, as the error occurs in Xvfb, not in Browservice itself. We could possibly patch both Xvfb and Chromium to use a different path for the sockets, but that is hacky and error-prone. I'm open to suggestions on better ways to make this work.
If the
wslu
support package is installed in a WSL2 guest, then/tmp/.X11-unix
is a symlink to/mnt/wslg/.X11-unix
, which is a read-only tmpfs mount.This causes browservice to fail like this:
The same error happens if
/mnt/wslg/.X11-unix
is remounted read-write.Browservice starts as expected if the
/tmp/.X11-unix
symlink is deleted such that the X11 stack recreates it as a directory, but that breaks Windows desktop integration with other Linux apps.Version info is:
I appreciate that running browservice in WSL2 is a corner case because it can run on the Windows host, but there might be a more general bug in how the
/tmp/.X11-unix
symlink is handled.