-
Notifications
You must be signed in to change notification settings - Fork 116
odd fontconfig cache location from appimage build #239
Comments
I'm not able to reproduce that, actually (using Ubuntu 20.04). I did have a folder |
I'm running Ubuntu 16.04 and Cura 4.6.1. I'm absolutely sure it's Cura. The only AppImage programs I run are Cura and OpenSCAD and I've been able to consistently reproduce that the cache directory is created every time I open Cura. My best guess is that since I don't have a ton of XDG-prefixed env vars defined, it's using a default value. But I'd say this is a poor default. I've seen other reports of similar behavior from other programs. |
What do you get when you run Our fontconfig should be on version 2.13, as that comes with the CentOS 7 installation that builds our AppImages. |
I also get an empty string. When I run
I also took a look at the strings in the |
The only reference I could find to |
Same behaviour here on Fedora 32 with the Cura 4.6.1 Appimage. echo $XDG_CACHE_HOME returns an empty string and the fontconfig version installed is fontconfig-2.13.92-9.fc32.x86_64. |
Same problem here, Manjaro running Plasma, |
This is a minor annoyance, but with the Linux AppImage build of Cura, the bundled libfontconfig is placing its cache directory in my home directory (
$HOME/fontconfig
) instead of utilizing the normal cache directory ($HOME/.cache/fontconfig
). I don't know if this is an issue with the version of libfontconfig that's being shipped or a configuration issue. I don't know if the issue is here or upstream. But it is annoying.The text was updated successfully, but these errors were encountered: