This issue is forced at the tinderbox (pls see bug #567192 too) by setting: export XDG_DESKTOP_DIR="/root/Desktop" export XDG_DOCUMENTS_DIR="/root/Documents" export XDG_DOWNLOAD_DIR="/root/Downloads" export XDG_MUSIC_DIR="/root/Music" export XDG_PICTURES_DIR="/root/Pictures" export XDG_PUBLICSHARE_DIR="/root/Public" export XDG_TEMPLATES_DIR="/root/Templates" export XDG_VIDEOS_DIR="/root/Videos" export XDG_RUNTIME_DIR="/root/run" export XDG_CONFIG_HOME="/root/config" export XDG_CACHE_HOME="/root/cache" export XDG_DATA_HOME="/root/share" sandbox output: VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: mkdir S: deny ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_abi32+64-test_20180203-182621 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv sys-apps/systemd [ebuild U ] sys-apps/systemd-237-r2 [237-r1] USE="acl gcrypt kmod lz4 pam pcre seccomp ssl sysv-utils -apparmor -audit -build -cryptsetup -curl -elfutils -gnuefi -http -idn -importd -libidn2 -lzma -nat -policykit -qrcode (-selinux) {-test} -usrmerge -vanilla -xkb" ABI_X86="32 (64) (-x32)"
Created attachment 518672 [details] emerge-info.txt
Created attachment 518674 [details] emerge-history.txt
Created attachment 518676 [details] etc.portage.tbz2
Created attachment 518678 [details] logs.tbz2
Created attachment 518680 [details] sandbox-13015.log
Created attachment 518682 [details] sys-apps:systemd-237-r2:20180208-182218.log
Please stop reporting this problem. I cannot reproduce it, and it only occurs on your tinderbox. You will need to provide additional debugging information. *** This bug has been marked as a duplicate of bug 627850 ***