Summary: | net-im/skype-4.2.0.11-r1: 'fontconfig' directory created in home directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | BT <amak79> |
Component: | Current packages | Assignee: | Ben de Groot (RETIRED) <yngwin> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | ganastasiouGR, help, samuel.bauer |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://cgit.freedesktop.org/fontconfig/commit/?id=3e5f70a16ac6d54f1e01c92ddaa5985deec1b7f9 | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=458104 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
BT
2013-10-04 06:38:22 UTC
I tried the suggestion from bug #458104 by adding ABI_X86="32 64" to make.conf but that doesn't appear to do anything. fontconfig still builds with ABI_X86="(64) (-32) (-x32)". The other suggestion to manually create a '~/.fontconfig' directory also doesn't help. I just realised that I had to rename the auto created 'fontconfig' directory to '.fontconfig'. This does "fix" the issue as the 'fontconfig' directory is no longer created. Just a guess, but could this be a problem that was fixed in fontconfig in "Do not create a config dir for migration when no config files nor dirs" commit (first after 2.10.95 tag) ? (In reply to Rafał Mużyło from comment #3) > Just a guess, but could this be a problem that was fixed in fontconfig in > "Do not create a config dir for migration when no config files nor dirs" > commit (first after 2.10.95 tag) ? Yes it does appear that the issue is fixed with that commit. I haven't been able to test it as there are too many changes since 2.10.93 to create a simple patch. Seems to be the same symptom related here: http://forums.debian.net/viewtopic.php?f=6&t=87548 FIX: sed -i '/prefix="xdg"/d' /etc/fonts/fonts.conf Please test fontconfig-2.11.0 and tell us whether this issue has been solved. (In reply to Ben de Groot from comment #6) > Please test fontconfig-2.11.0 and tell us whether this issue has been solved. Unfortunately the issue is still present with fontconfig-2.11.0. *** This bug has been marked as a duplicate of bug 486338 *** |