[pkg-wine-party] Bug#813381: fonts-wine: freetype_SelectFont can't find a single appropriate font

Jens Reyer jre.winesim at gmail.com
Tue Feb 9 04:31:58 UTC 2016


control: tags -1 - moreinfo

On 02/08/2016 10:42 PM, Johannes Stezenbach wrote:
> I just ran into the same issue, and after some
> experiments found it is caused by a missing libfontconfig1.
> libfontconfig1:i386 is only in Recommends of libwine:i386,
> but it should be in Depends.
> Same for libwine-development (1.9.0-2).

Hi,

thanks a lot Johannes. I can confirm this now, if I install only the
32-bit packages and uninstall libfontconfig1:i386.

In 1.8-6 if libfontconfig1:i386 is not installed, but fonts-wine is
installed, this doesn't happen. However another font is used then.

tl;dr: There are two issues that should be fixed. I suggest to depend on
libfontconfig1 to make the system fonts available, and to revert the
fonts related changes to make the Wine fonts available. Better
solutions/analysis welcome.

1.)
libfontconfig1 is needed to use the Linux system fonts. Although you can
use 64-bit prefixes just fine even if only libfontconfig1:amd64 is
installed, I think we should make sure that the system fonts *always*
work in Wine (the Wine font used as fallback in winefile is really
ugly). Or is there any use case for wanting to disable them? Otherwise
I'd suggest to depend on libfontconfig1.
I assume this just wasn't reported before, because:

2a)
Without libfontconfig1 in 1.8-6 the Wine fonts were still found, but
aren't now. Looks as if something is broken (the fontdir seems to be
correctly set in the Makefile, so I wonder if Wine has some other
internals that require/exclude a specific fontdir).

2b)
Even if we decided to ignore that problem, and chose to use the Wine
fonts via fontconfig (if that really works the same way for Wine without
drawbacks), we would probably have a new problem: per default fontconfig
doesn't include bitmapped fonts anymore (see
/usr/share/doc/fontconfig/README.Debian). But afaics the Wine fonts are
bitmap fonts. Currently I can only assume this to be a problem, any idea
how to explicitly test the Wine fonts?

If 2a is fixed, 2b won't be a problem. For now my only idea is to revert
that change, although I generally like the idea of the common
fonts-wine, with fonts in /usr/share/fonts (I assume this is not a
strict requirement, didn't check, though).

Greets
jre



More information about the pkg-wine-party mailing list