Just to be sure, is XDG_RUNTIME_DIR kept in the environment after you sudo? `sudo -E' (or adding it to env_keep in sudoers) should do it.

(For bonus info, try strace -e connect paplay ... inside the chroot -- it should have a line with sun_path="$XDG_RUNTIME_DIR/pulse/native").

I've renamed the ...

The udev daemon automatically loads all needed kernel modules.


Is this considered to be more portable or sane? I don't have anything in /etc/modules-load.d nor /usr/lib/modules-load.d either.

It's the foundation of hotplugging and automatic hardware detection on Linux. It's perfectly fine ...

Arch wiki people report also needing to bind /var/lib/dbus inside the chroot. PA in my chroot works just fine without it, but it might help you.

While you're at it, does paplay some_file.wav work in your chroot?

The quickest solution is running your chroot under your UID. By default, XDG_RUNTIME_DIR (where the D-Bus and PA IPC endpoints are located - usually /run/user/$(id -u)) can only be accessed by your UID, so applications under your "steam" UID are locked out of it.

If you're chrooting steam for ...

Try compressing it with bzip2 or brotli -9 and sending it to a more "general" file uploading service (like ix.io). Or `awk /error:/,0` the file so it only prints starting from the C compiler/preprocessor errors (which are the usual source of configure issues).

It's the ffbuild/config.log file, which is located in the working directory.

Both are mentioned in the build.log.

There's one thing I'm curious about that I can't find in the documentation for s6 is nested services.

If you look at Artix's iwd it's structure looks like this:


- iwd
--- iwd-log
----- consumer-for
----- notification-fd
----- pipeline-name
----- run
----- type
--- iwd-srv
----- dependendies.d ...