You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default xorg opens '/tmp/.X11-unix/X«display number»' as both an abstract namespace and a filesystem based domain socket. If you're running in a snap container you're able to access the abstract namespace socket but not the filesystem socket. (Abstract namespace domain sockets show up as @''/tmp/.X11-unix/X«display number»', but effectively just have a null byte as the first character in the sun_path field, see http://man7.org/linux/man-pages/man7/unix.7.html).
It'd be nice to have node-x11 support the abstract namespace versions of the x11 socket.
There's an NPM module, abstract-socket, that might be useful.
The text was updated successfully, but these errors were encountered:
By default xorg opens
'/tmp/.X11-unix/X«display number»'
as both an abstract namespace and a filesystem based domain socket. If you're running in a snap container you're able to access the abstract namespace socket but not the filesystem socket. (Abstract namespace domain sockets show up as@''/tmp/.X11-unix/X«display number»'
, but effectively just have a null byte as the first character in thesun_path
field, see http://man7.org/linux/man-pages/man7/unix.7.html).It'd be nice to have node-x11 support the abstract namespace versions of the x11 socket.
There's an NPM module, abstract-socket, that might be useful.
The text was updated successfully, but these errors were encountered: