FS#42542 - [fontconfig][xfig] fonts problem

Attached to Project: Arch Linux
Opened by Yannick Alméras (alfazaz) - Saturday, 25 October 2014, 08:36 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 14 March 2016, 16:07 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Eric Belanger (Snowman)
Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
When we want to type text, we get wrong fonts... I think the problem appeared with latest upgrade of gsfonts package...

Additional info:
* package version(s) : xfig-3.2.5c-2

Steps to reproduce:
* Get an up to date arch linux with xfig
* Open xfig
* Select Text icon
* Type text and see bad fonts...
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 14 March 2016, 16:07 GMT
Reason for closing:  Fixed
Comment by Albert Lienardi (albertlienardi) - Monday, 27 October 2014, 11:21 GMT
The problem came from different font names used in the fonts provided by the latest gsfonts package which calls for a proper font mapping by fontconfig. See this https://bugs.freedesktop.org/show_bug.cgi?id=85225 as a reference.
Comment by mattia (nTia89) - Wednesday, 19 November 2014, 20:30 GMT
I confirm the issue:
bug in fontconfig seems to be fixed in git, so or we include the patch or we wait until a new release...
Comment by Michael Herman (mherman_nm) - Wednesday, 04 February 2015, 23:04 GMT
I confirm the font issue. Changing the font has no effect. However, I also get the following just running xfig:

xfig3.2.5c: SIGSEGV signal trapped
xfig: Figure is empty or not modified - exiting without saving.
Segmentation fault (core dumped)
Comment by Andreas Radke (AndyRTR) - Saturday, 18 April 2015, 07:55 GMT Comment by Yannick Alméras (alfazaz) - Saturday, 18 April 2015, 13:52 GMT
I can try anything if you tell me steps to follow... Thanks !
Comment by Andreas Radke (AndyRTR) - Saturday, 18 April 2015, 17:22 GMT
Use abs to rebuild the Arch package and add the upstream patch for testing.
Comment by Yannick Alméras (alfazaz) - Saturday, 18 April 2015, 19:22 GMT
I tried it and it failed on applying patch :

*****************
[yannick@portable fontconfig ]$ makepkg
==> Création du paquet fontconfig 2.11.1-1 (sam. avril 18 21:20:06 CEST 2015)
==> Vérification des dépendances pour l’exécution...
==> Vérification des dépendances pour la compilation...
==> Récupération des sources...
-> fontconfig-2.11.1.tar.bz2 trouvé
==> Validation des fichiers sources avec sha256sums...
fontconfig-2.11.1.tar.bz2 ... Réussite
==> Extraction des sources...
-> Extraction de fontconfig-2.11.1.tar.bz2 avec bsdtar
==> Lancement de prepare()...
patching file conf.d/30-metric-aliases.conf
Hunk #4 succeeded at 94 with fuzz 2 (offset 2 lines).
Hunk #5 succeeded at 116 (offset 3 lines).
Hunk #6 succeeded at 144 (offset 3 lines).
Hunk #7 succeeded at 172 (offset 3 lines).
Hunk #8 succeeded at 207 (offset 3 lines).
Hunk #9 succeeded at 228 (offset 3 lines).
Hunk #10 succeeded at 256 (offset 3 lines).
Hunk #11 succeeded at 467 (offset 3 lines).
Hunk #12 succeeded at 476 (offset 3 lines).
Hunk #13 FAILED at 481.
Hunk #14 succeeded at 495 (offset 6 lines).
Hunk #15 succeeded at 504 (offset 6 lines).
Hunk #16 succeeded at 514 (offset 6 lines).
Hunk #17 succeeded at 523 (offset 6 lines).
Hunk #18 succeeded at 533 (offset 6 lines).
Hunk #19 succeeded at 543 (offset 6 lines).
1 out of 19 hunks FAILED -- saving rejects to file conf.d/30-metric-aliases.conf.rej
patching file conf.d/45-latin.conf
Hunk #2 succeeded at 105 (offset 4 lines).
patching file conf.d/60-latin.conf
==> ERREUR : Une erreur s’est produite dans prepare().
Abandon...
**************************

I made what mistake ?
Comment by David Bernecker (derberni) - Tuesday, 23 June 2015, 16:12 GMT
I just built the fontconfig 2.11.94 version (which includes the patch mentioned above) as a package and replaced my regular fontconfig package.

However, I still have the issue that fonts do not change in xfig. Could I have missed anything?
Comment by Albert Lienardi (albertlienardi) - Tuesday, 23 June 2015, 16:20 GMT
Have you tried to update the font cache?
Comment by David Bernecker (derberni) - Tuesday, 23 June 2015, 18:35 GMT
Yes, I did run fc-cache -f after installing the package.
Comment by Dimitris Dracopoulos (ddracopo) - Sunday, 28 June 2015, 17:58 GMT
Same problem in here. Upgrading to 2.11.94 and updating the font cache does not solve the problem. Any ideas?

pacman -Ss xfig
extra/potrace 1.11-2 [installed]
Utility for tracing a bitmap (input: PBM,PGM,PPM,BMP; output:
EPS,PS,PDF,SVG,DXF,PGM,Gimppath,XFig)
extra/transfig 3.2.5e-1 [installed]
Format conversion utility that can be used with xfig
extra/xfig 3.2.5c-2 [installed]
An interactive drawing tool

pacman -Ss fontconfig
extra/fontconfig 2.11.1-1 [installed: 2.11.94-1]
A library for configuring and customizing font access
multilib/lib32-fontconfig 2.11.1-1 [installed]
A library for configuring and customizing font access (32-bit)

Comment by Andreas Radke (AndyRTR) - Sunday, 13 March 2016, 17:42 GMT
Fontconfig 2.11.94 is now in testing repo. The PKGBUILD is also prepared to build from git master. Feel free to recheck against current git master status. If it's still broken you should check the bug to be at the xfig side.
Comment by Dimitris Dracopoulos (ddracopo) - Monday, 14 March 2016, 15:28 GMT
The problem has been fixed before this. I am not sure what caused the fix but the problem is not there having installed fontconfig 2.11.1-2 currently

Update in March 2017: It seems the problem is related to gsfonts. It came back after some updates. However:

installing the gsfonts-type1 package from AUR and removing the gsfonts package (they are in conflict) solves the problem. You need to restart X or simply:

xset +fp /usr/share/fonts/Type1
xset fp rehash

and restart xfig.

Loading...