I found the following errors when executing ejabberd's captcha script: convert: unable to read font `/usr/lib/ImageMagick-6.6.1/config//usr/share/fonts/corefonts/arial.ttf' @ error/annotate.c/RenderFreetype/1056. convert: unable to read font `/usr/lib/ImageMagick-6.6.1/config//usr/share/fonts/corefonts/arial.ttf' @ error/annotate.c/RenderFreetype/1056. convert: unable to read font `/usr/lib/ImageMagick-6.6.1/config//usr/share/fonts/corefonts/arial.ttf' @ error/annotate.c/RenderFreetype/1056. convert: unable to read font `/usr/lib/ImageMagick-6.6.1/config//usr/share/fonts/corefonts/arial.ttf' @ error/annotate.c/RenderFreetype/1056. It seems to be related to imagemagick mistreating absolute paths in the "glyphs" attribute to the "type" element: /usr/lib/ImageMagick-6.6.1/config/type-windows.xml: <type name="Arial" fullname="Arial" family="Arial" weight="400" style="normal" stretch="normal" glyphs="/usr/share/fonts/corefonts/arial.ttf"/> Reproducible: Always
Created attachment 234677 [details] ejabberd-2.1.4 captcha.sh
I got the same problem on amd64 box with a fresh gentoo from portage-20100704.tar.bz2 stage3-amd64-20100408.tar.bz2 The problem lies in that the imagemagick ebuild does not depend on media-fonts/corefonts. This would not be a problem is some other ebuild brings in media-fonts/corefonts. But in your case and my case this does not happen. The fix is to put media-fonts/corefonts as a dependency in the ebuild (sorry I don't know how to do that right now as to provide a patch). The temporal fix for the affected box is to do an "emerge corefonts" and problem solved. HTH. (In reply to comment #1) > Created an attachment (id=234677) [details] > ejabberd-2.1.4 captcha.sh > (In reply to comment #0) > I found the following errors when executing ejabberd's captcha script: > convert: unable to read font > `/usr/lib/ImageMagick-6.6.1/config//usr/share/fonts/corefonts/arial.ttf' @ > error/annotate.c/RenderFreetype/1056. > convert: unable to read font > `/usr/lib/ImageMagick-6.6.1/config//usr/share/fonts/corefonts/arial.ttf' @ > error/annotate.c/RenderFreetype/1056. > convert: unable to read font > `/usr/lib/ImageMagick-6.6.1/config//usr/share/fonts/corefonts/arial.ttf' @ > error/annotate.c/RenderFreetype/1056. > convert: unable to read font > `/usr/lib/ImageMagick-6.6.1/config//usr/share/fonts/corefonts/arial.ttf' @ > error/annotate.c/RenderFreetype/1056. > > It seems to be related to imagemagick mistreating absolute paths in the > "glyphs" attribute to the "type" element: > /usr/lib/ImageMagick-6.6.1/config/type-windows.xml: <type name="Arial" > fullname="Arial" family="Arial" weight="400" style="normal" stretch="normal" > glyphs="/usr/share/fonts/corefonts/arial.ttf"/> > > > Reproducible: Always >
sounds like ejabberd is the one with missing corefonts depend... having it in imagemagick's ebuild doesn't change the end result at all (imagemagick will be the same, with or without corefonts). just another pointless USE flag doing nothing... uh
ejabberd's bug was one thing, but I had the same problem on a different situation. I installed a Gentoo system without conventional desktop (no gnome nor kde nor xfce) and lo behold, imagemagick was borked because corefonts was not pulled in during ebuilds.
*imagemagick-6.6.3.0 (26 Jul 2010) 26 Jul 2010; Samuli Suominen <ssuominen@gentoo.org> +imagemagick-6.6.3.0.ebuild, metadata.xml: Version bump with reintroduced coreutils USE flag wrt #323309 by Dennis Schridde.
