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

2016-02-11 Thread Jens Reyer
I tested it further: I completly emptied /usr/share/fonts. Then, only
the font family "Latin Modern (LM)" (installed in
/usr/share/texmf/fonts) is available and used. I checked this in the
font selection dialogs of libreoffice (Linux native) and winefile.

Then I installed wine 1.8-6 with fonts-wine 1.8-6:
this correctly adds several fonts in winefile.

However with wine 1.8.1-1 and fonts-wine 1.8.1-1 installed, even with
- libfontconfig1 (amd64 and i386) installed and
- enabled bitmapped fonts in "dpkg-reconfigure fontconfig-config",
there are no additional fonts available, neither in winefile, nor
in libreoffice.

For Wine to work either the system fonts or wine-fonts *must* work. The
system fonts imo provide a much superior result. I therefore committed
the change for libwine to always depend on libfontconfig1 (so you end up
with e.g. both the i386 and the amd64 version).
The 32-bit version inadvertently missing happens too easily and has too
severe drawbacks, compared to the benefits of not installing this
package and using only fonts-wine - imo this justifies the promotion
from recommends to depends.

However, to close this bug we should also fix fonts-wine. Even in an
afaics correctly set up system these fonts never show up, neither in
wine nor in the system. I have absolutely no clue how to make them in
the new position in /usr/share/fonts/wine work.
But I found this changelog entry from 2006:
---
 * Wine now install its fonts under /usr/share/wine/fonts, not
/usr/share/fonts/wine. (I've updated the packaging accordingly.)
This should stop them from being picked up by fontconfig et al.
Closes: #353495.
---
The fonts were removed from the new position previously on purpose,
because they weren't correctly rendered in some native apps.

Greets
jre



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

2016-02-08 Thread Jens Reyer
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



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

2016-02-08 Thread Johannes Stezenbach
Package: libwine
Version: 1.8.1-1
Followup-For: Bug #813381

Dear Maintainer,

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).

(And of course I had libfontconfig1 installed for amd64, but
not for i386.)


HTH,
Johannes



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

2016-02-07 Thread Bjørn Mork
Jens Reyer  writes:

> prefix and update to 1.8-7 or 1.8.1-1. I also don't get the fixme
> warnings (although enabled in WINEDEBUG).
>
> But other Windows applications indeed also miss the text in their
> windows. Creating the link doesn't help though for that.

Thanks for testing.  Any ideas about other places I might have messed
up, making this problem happen?  I must admit that I don't have a
perfectly "clean" sid or testing system. There are still some jessie
packages around. Although I have made an effort to align all wine related
packacges with sid, I might have missed something.

> I have fonts-liberation installed (but not ttf-mscorefonts-installer).
> Unfortunately I can't easily test if this is the reason that I don't see
> exactly the same problem. Do you have fonts-liberation installed?

I have both those packages installed:

bjorn@nemi:~$ apt-cache policy fonts-liberation ttf-mscorefonts-installer
fonts-liberation:
  Installed: 1.07.4-1
  Candidate: 1.07.4-1
  Version table:
 *** 1.07.4-1 700
700 http://ftp.no.debian.org/debian jessie/main amd64 Packages
700 http://ftp.no.debian.org/debian jessie/main i386 Packages
600 http://ftp.no.debian.org/debian sid/main amd64 Packages
600 http://ftp.no.debian.org/debian sid/main i386 Packages
100 /var/lib/dpkg/status
ttf-mscorefonts-installer:
  Installed: 3.6
  Candidate: 3.6
  Version table:
 *** 3.6 700
700 http://ftp.no.debian.org/debian jessie/contrib amd64 Packages
700 http://ftp.no.debian.org/debian jessie/contrib i386 Packages
600 http://ftp.no.debian.org/debian sid/contrib amd64 Packages
600 http://ftp.no.debian.org/debian sid/contrib i386 Packages
100 /var/lib/dpkg/status


Bjørn



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

2016-02-06 Thread Jens Reyer
On 02/01/2016 03:21 PM, Bjørn Mork wrote:
> Package: fonts-wine
> Version: 1.8-7
> Severity: important
> 
> Upgrading fonts-wine from 1.8-6 to 1.8-7 breaks wine. 
> 
> Running e.g. winefile with  WINEDEBUG=warn+all results in lots of
> warnings like this:
> 
>  fixme:font:freetype_SelectFont can't find a single appropriate font - bailing
> 
> and a mostly empty application window.  Downgrading fonts-wine to 1.8-6
> fixes the problem.  So does 
> 
>  /usr/share/wine/wine
>  ln -s ../../fonts/wine fonts
> 
> Looks like the move to /usr/share/fonts wasn't complete?

winecfg or winefile look ok here, even if I start with 1.8-6, create a
prefix and update to 1.8-7 or 1.8.1-1. I also don't get the fixme
warnings (although enabled in WINEDEBUG).

But other Windows applications indeed also miss the text in their
windows. Creating the link doesn't help though for that.

I have fonts-liberation installed (but not ttf-mscorefonts-installer).
Unfortunately I can't easily test if this is the reason that I don't see
exactly the same problem. Do you have fonts-liberation installed?

btw 1, packages.d.o [1] strangely still shows the old filepaths (up to
1.8-6), e.g. /usr/share/wine/wine/fonts/vgasyst.fon. But I don't see how
this could be related.

btw 2, wine-development has fontdir = /usr/share/wine/wine/fonts.

Greets
jre

[1]: https://packages.debian.org/sid/all/fonts-wine/filelist



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

2016-02-02 Thread Bjørn Mork
Michael Gilbert  writes:
> On Mon, Feb 1, 2016 at 9:21 AM, Bjørn Mork wrote:
>> Running e.g. winefile with  WINEDEBUG=warn+all results in lots of
>> warnings like this:
>>
>>  fixme:font:freetype_SelectFont can't find a single appropriate font - 
>> bailing
>
> You may need to run winecfg to update an existing config.  Please
> reply whether that works, and I'll document it.

But winecfg is offer for the same problem, like any other windows
application...

Attempting to run winecfg with fonts-wine version 1.8-7 and no
/usr/share/wine/wine/fonts symlink results in the same fonts warnings
and no visible application window at all.

Not that I think it would help anyway.  I cannot see anywhere the font
path configured in winecfg.  I also tried looking around for registry
settings etc before downgrading fonts-wine, without finding anything
that looked like it pointed to the fonts dir.



Bjørn



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

2016-02-02 Thread Austin English
On Feb 2, 2016 6:00 AM, "Michael Gilbert"  wrote:
>
> control: tag -1 moreinfo
>
> On Mon, Feb 1, 2016 at 9:21 AM, Bjørn Mork wrote:
> > Running e.g. winefile with  WINEDEBUG=warn+all results in lots of
> > warnings like this:
> >
> >  fixme:font:freetype_SelectFont can't find a single appropriate font -
bailing
>
> You may need to run winecfg to update an existing config.  Please
> reply whether that works, and I'll document it.

You might want wineboot -u, which winecfg should invoke if the wine version
changed, but might as well be explicit :)


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

2016-02-01 Thread Michael Gilbert
control: tag -1 moreinfo

On Mon, Feb 1, 2016 at 9:21 AM, Bjørn Mork wrote:
> Running e.g. winefile with  WINEDEBUG=warn+all results in lots of
> warnings like this:
>
>  fixme:font:freetype_SelectFont can't find a single appropriate font - bailing

You may need to run winecfg to update an existing config.  Please
reply whether that works, and I'll document it.

Best wishes,
Mike



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

2016-02-01 Thread Bjørn Mork
Package: fonts-wine
Version: 1.8-7
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Upgrading fonts-wine from 1.8-6 to 1.8-7 breaks wine. 

Running e.g. winefile with  WINEDEBUG=warn+all results in lots of
warnings like this:

 fixme:font:freetype_SelectFont can't find a single appropriate font - bailing

and a mostly empty application window.  Downgrading fonts-wine to 1.8-6
fixes the problem.  So does 

 /usr/share/wine/wine
 ln -s ../../fonts/wine fonts

Looks like the move to /usr/share/fonts wasn't complete?


Bjørn

- -- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500, 
'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc2+ (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages fonts-wine is related to:
ii  fonts-wine1.8-7
ii  libwine   1.8-7
pn  libwine-dbg   
pn  libwine-dev   
ii  wine  1.8-7
ii  wine321.8-7
pn  wine32-preloader  
pn  wine32-tools  
ii  wine641.8-7
pn  wine64-preloader  
pn  wine64-tools  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iEYEARECAAYFAlavaccACgkQ10rqkowbIsn1zwCfQSK2vdoPqvOZBN9S8MNPk9Xx
DRQAnR9PHb3naoPI7kTNixbwEEeS3a4F
=l48r
-END PGP SIGNATURE-