Commit 0e2b24c
committed
wslg-permissions-fix.service: also bind-mount /tmp/.X11-unix (flatpak bwrap fix)
Operator-flagged 2026-05-10 launching Nautilus.Devel:
bwrap: Can't mount tmpfs on /newroot/tmp/.X11-unix: No such file or directory
WSL2 ships /tmp/.X11-unix as a SYMLINK -> /mnt/wslg/.X11-unix. Most
flatpak GUI apps tolerate the symlink because bwrap follows it
during mount-prep. But some (Nautilus.Devel from gnome-nightly,
gnome-text-editor, X11-fallback apps) explicitly try to tmpfs-mount
/newroot/tmp/.X11-unix inside their chroot -- which fails because
you can't tmpfs over a symlink in bwrap's namespace setup.
Fix: at the same boot phase as the runtime-dir chmod, replace the
WSL-shipped symlink with a real directory + bind-mount the host's
/mnt/wslg/.X11-unix onto it. From the flatpak's perspective
/tmp/.X11-unix is now a regular dir containing the X0 socket --
bwrap can tmpfs over it freely, and the socket inside is the
correct host-side WSLg one.
Operator-verified live 2026-05-10: after this fix Nautilus.Devel
launches without the bwrap error; bwrap chains advance to a
sandboxed nautilus process that registers with weston correctly.1 parent aa4e658 commit 0e2b24c
1 file changed
Lines changed: 16 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
33 | 33 | | |
34 | 34 | | |
35 | 35 | | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
36 | 52 | | |
37 | 53 | | |
38 | 54 | | |
| |||
0 commit comments