Bug 1011127

Summary:	fontconfig isn’t able to follow symbolic link
Product:	[Fedora] Fedora	Reporter:	Pablo Rodríguez <ousia>
Component:	fontconfig	Assignee:	Akira TAGOH <tagoh>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	19	CC:	fonts-bugs, i18n-bugs, ousia, pnemade, tagoh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-24 19:09:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Pablo Rodríguez 2013-09-23 16:20:18 UTC

I guess this isn’t a proper issue against fontconfig, but I’m experiencing this with it. (Please, replace component accordingly, if it’s wrong.)

One of the system directories containing fonts (/usr/share/fonts/ousia-fonts/) is actually a soft symbolic link to /home/ousia/Documents/ousia-fonts/. Owner is set to root and permissions are right.

This worked fine with Fedora 16, but after moving to Fedora 19 it doesn’t work.

Even listing directories doesn’t work.

What is wrong here?

Many thanks for your help,


Pablo

Comment 1 Akira TAGOH 2013-09-24 07:25:05 UTC

that looks like working for me. please make sure if the output of fc-cache -vf /usr/share/fonts contains that directory and see it creates a cache for that. then it might be another issue I imagine.

Comment 2 Pablo Rodríguez 2013-09-24 19:09:13 UTC

Akira,

sorry for the noise, it was totally my fault: missing execution permissions on the font directory itself.

May I ask which was the issue you imagined?

I’m closing the bug myself.

Sorry for the noise again,


Pablo