Bug 1195652

Hi Stephen,

I'm not able to reproduce it here. It would help me to know which font exactly causes the problem. I think that ftview could help to narrow it.
Could you try to look which font in "/usr/share/X11/fonts/misc/" renders wrong by running "ftview 13 /usr/share/X11/fonts/misc/a-6x13-font" for each of those 6x13 fonts (or another one if you have it in a custom directory (e.g. ~/.fonts/)) ?

Regards

Marek

ftview helped narrow things down, thanks.  Curious.

So it turns out I did have a copy of 6x13.pcf in ~/.fonts/.  With downgraded freetype, I can ftview it fine.  With the latest freetype, I cannot:

$ ftview 13 6x13.pcf 
could not find/open any font file
  error = 0x0002
$ strace ftview 13 6x13.pcf 
...
open("6x13.pcf", O_RDONLY)              = 3
fcntl(3, F_SETFD, FD_CLOEXEC)           = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=470612, ...}) = 0
mmap(NULL, 470612, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f0d0d772000
close(3)                                = 0
mmap(NULL, 282624, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f0d0d72d000
munmap(0x7f0d0d72d000, 282624)          = 0
open("._6x13.pcf", O_RDONLY)            = -1 ENOENT (No such file or directory)
open("%6x13.pcf", O_RDONLY)             = -1 ENOENT (No such file or directory)
open(".AppleDouble/6x13.pcf", O_RDONLY) = -1 ENOENT (No such file or directory)
open("6x13.pcf/..namedfork/rsrc", O_RDONLY) = -1 ENOTDIR (Not a directory)
open("6x13.pcf/rsrc", O_RDONLY)         = -1 ENOTDIR (Not a directory)
open("resource.frk/6x13.pcf", O_RDONLY) = -1 ENOENT (No such file or directory)
open(".resource/6x13.pcf", O_RDONLY)    = -1 ENOENT (No such file or directory)
munmap(0x7f0d0d772000, 470612)          = 0
write(2, "could not find/open any font fil"..., 51could not find/open any font file

I tried symlinking the /usr/share/X11/fonts/misc/6x13.pcf.gz file into my ~/.fonts (removing the old 6x13.pcf)... it works fine.

Could the .gz be the difference?

And yes ---

$ ftview 13 6x13.pcf 
could not find/open any font file
  error = 0x0002
$ gzip -v9 6x13.pcf 
6x13.pcf:	 85.5% -- replaced with 6x13.pcf.gz
[sct@herobrine tmp]$ ftview 13 6x13.pcf.gz 

works fine.  The exact same font file works compressed, but fails to open uncompressed.  With downgraded freetype, both work fine.

Anyway, this workaround gets me back up and running now; but I'll leave the BZ open as there's clearly still an issue here.  Thanks!

Thank you very much for all the information. I've been able to find the patch which unveiled the problem [1] thanks to that and also to backport fixes for it [2][3].
This should be fixed in freetype-2.5.3-16.fc21 and in freetype-2.5.0-10.fc20.

Regards

Marek


[1] http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=0e2f5d518c60e2978f26400d110eff178fa7e3c3

[2] http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=74af85c4b62b35e55b0ce9dec55ee10cbc4962a2

[3] http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=06842c7b49c21f13c0ab61201daab6ff5a358fcc

freetype-2.5.3-16.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/freetype-2.5.3-16.fc21

freetype-2.5.0-10.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/freetype-2.5.0-10.fc20

Many thanks!  This is confirmed fixed in freetype-2.5.3-16.fc21 from koji.  Karma left.

Package freetype-2.5.3-16.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing freetype-2.5.3-16.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-2481/freetype-2.5.3-16.fc21
then log in and leave karma (feedback).

freetype-2.5.3-16.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

freetype-2.5.0-10.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.