I chose wrong release .It's the 2018.4 not 2018.1 .

In VirtualBox 5.2.20 when booting from ISO in live mode, there is the same bug!

This also occurs on arm64.

A workaround exists by killing xfsettingsd and then relaunching it, but it comes back after a logout/login.

Another workaround is downgrading libfontconfig1 and fontconfig to 2.30, however it's not a good workaround as 2.30 crashes on empty font folders.

Hey . How can it down grade ? Use dpkg remove --force-depends and install fontconfig.deb ?

You would need to download the 2.13.0 version from Debian's servers. You can see what I do in the raspberrypi3 64bit image at

https://github.com/offensive-security/kali-arm-build-scripts/blob/master/rpi3-64.sh#L188-L189 for the wgets (obviously you'd want to choose the architecture you're running on!)
and then see
https://github.com/offensive-security/kali-arm-build-scripts/blob/master/rpi3-64.sh#L232-L234 for how I install them (just apt install with the fixed path on the file system)

Oh .thanks

Looks like Debian have fixed the issue in 2.13.1-2 upstream, so as soon as we pull that in, you shouldn't see this issue anymore (though you'll likely have to reboot/restart your login manager for the new fontconfig)

Upstream debian bug is Bug# 909818

Looks like the updated packages are on the mirrors, thanks for the report, please be sure to apt-get update && apt-get dist-upgrade to pull in the fixed version of fontconfig.