Bug 9974 - fontconfig shows a very annoying message
Summary: fontconfig shows a very annoying message
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: High major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: NEEDINFO MGA3TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-03 20:50 CEST by Thomas Spuhler
Modified: 2014-04-13 18:05 CEST (History)
10 users (show)

See Also:
Source RPM: fontconfig
CVE:
Status comment:


Attachments
patch (1.06 KB, patch)
2013-05-04 01:37 CEST, Barry Jackson
Details | Diff
file tat reports the problem (490 bytes, text/plain)
2013-05-04 18:46 CEST, Thomas Spuhler
Details

Description Thomas Spuhler 2013-05-03 20:50:49 CEST
Description of problem:
compiling a lilypond file shows this message:
$ lilypond score.ly 
GNU LilyPond 2.16.1
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.


Version-Release number of selected component (if applicable):
current cauldron (RC) and only 64 bit

How reproducible:
Every time on a 64bit box I just did a fresh install

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Barry Jackson 2013-05-04 01:37:55 CEST
Created attachment 3881 [details]
patch

Ah - I came here with a possible fix for another fontconfig bug. not actually this one.

I fixed this ages ago on my machine by just deleting line 9 of /etc/fonts/conf.d/50-user.conf - I have not seen any bad side effects.

The other problem concerns more annoying messages which are fixed by the patch that I have attached here, however there are two possible ways to view this logically and I may have picked the wrong one, so don't just apply it without checking. I don't know enough about this to be sure.
It does fix the annoying messages but may break it's intended purpose.

CC: (none) => zen25000

Comment 2 Funda Wang 2013-05-04 06:20:43 CEST
Reporter, please attach your /etc/fonts/conf.d/50-user.conf.

CC: (none) => fundawang

Comment 3 Barry Jackson 2013-05-04 13:18:34 CEST
Funda - This is the warning that is removed by the patch I attached in #1 (see note)

Fontconfig warning: "/etc/fonts/conf.d/65-google-droid-sans.conf", line 61: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-google-droid-sans.conf", line 96: Having multiple values in <test> isn't supported and may not work as expected


Here is a default 50-user.conf that creates the reporter's warning

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
	<!-- Load per-user customization file -->
	<include ignore_missing="yes" prefix="xdg">fontconfig/conf.d</include>
	<include ignore_missing="yes" prefix="xdg">fontconfig/fonts.conf</include>
	<!-- the following elements will be removed in the future -->
	<include ignore_missing="yes" deprecated="yes">~/.fonts.conf.d</include>
	<include ignore_missing="yes" deprecated="yes">~/.fonts.conf</include>
</fontconfig>
Comment 4 Thomas Spuhler 2013-05-04 18:46:56 CEST
Created attachment 3887 [details]
file tat reports the problem

here is the 50--user.conf.
Please note (mentioned earlier) the message come up on 64 bit boxes only, and this is a May3rd, 2013 install from cauldron
Comment 5 Thomas Spuhler 2013-05-13 23:16:48 CEST
I am increasing Priority. This is very embarrassing when using a program that needs to run in command mode.

Priority: Normal => High
Severity: normal => major

Comment 6 Henrik Christiansen 2013-05-25 10:29:41 CEST
Mageia 3 upgraded from mageia 2.

i586 has the same error:

smplayer
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/65-google-droid-sans.conf", line 61: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-google-droid-sans.conf", line 96: Having multiple values in <test> isn't supported and may not work as expected

CC: (none) => hc

Remco Rijnders 2013-05-25 13:09:09 CEST

Assignee: bugsquad => dmorganec

Comment 7 Dick Gevers 2013-05-25 22:01:42 CEST
I adit I do not understand lots of it, but it seems this is the upstream bug, which is resolved fixed:

https://bugs.freedesktop.org/show_bug.cgi?id=33644

CC: (none) => dvgevers

Comment 8 Barry Jackson 2013-05-25 22:29:06 CEST
(In reply to Dick Gevers from comment #7)
> I adit I do not understand lots of it, but it seems this is the upstream
> bug, which is resolved fixed:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=33644

I think the annoying messages are the result of that "fix" ;)

Could someone confirm that my attached patch for this does (or does not) work correctly to work around this issue?

It certainly removes the messages, but I'm not certain that the logic is correct.
Comment 9 Dick Gevers 2013-05-26 21:49:55 CEST
fontconfig-2.10.93-1.mga4 is now available. Please check and tell if this changes the reported problem or not. Thanks

Whiteboard: (none) => NEEDINFO

Dimitrios Glentadakis 2013-06-08 18:02:36 CEST

CC: (none) => dglent

Comment 10 Thomas Spuhler 2013-06-08 18:19:22 CEST
I currently do not have a VM where a 32 bit ssytem is installed.
The problem only shows on 32 bit.
Comment 11 Thomas Spuhler 2013-06-08 18:24:19 CEST
(In reply to Thomas Spuhler from comment #10)
> I currently do not have a VM where a 32 bit ssytem is installed.
> The problem only shows on 32 bit.

Ooops, vice versa. I am going to test it right now
Comment 12 Thomas Spuhler 2013-06-08 21:23:41 CEST
Looks,the upgrade to fontconfig-2.10.93 (in Cauldron) from 2.10.2 in mga3 fixed it.
Comment 13 claire robinson 2013-07-22 15:34:10 CEST
This affects mga3 too, it's quite annoying. Is there any info needed, it's marked as NEEDINFO ?

CC: (none) => eeeemail
Whiteboard: NEEDINFO => NEEDINFO MGA3TOO

Comment 14 Thomas Spuhler 2013-08-17 02:48:54 CEST
This has been lying around for ever. I don't have a 32bit installation to check if it has been fixed in mga3
D Morgan 2013-09-18 00:17:00 CEST

Assignee: dmorganec => bugsquad

Comment 15 Dimitrios Glentadakis 2013-10-06 08:01:42 CEST
If i comment the line:
	<include ignore_missing="yes" deprecated="yes">~/.fonts.conf</include>

after my fonts are broken.
I reenabled it and i just changed the deprecated="yes" to "no"
Comment 16 Dave Hodgins 2013-10-16 06:20:23 CEST
I'm not sure what changed in the last week or so, but the script I've been
working on for copying iso images to usb drives stopped working.

It uses either dialog, or Xidalog which returns it's results on stderr.

Any invocation of Xdialog is now returning 
Fontconfig warning: "/etc/fonts/conf.d/65-4-sazanami-gothic.conf", line 8: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-4-sazanami-mincho.conf", line 8: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-google-droid-sans.conf", line 61: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-google-droid-sans.conf", line 96: Having multiple values in <test> isn't supported and may not work as expected

This is breaking the script, so I will be changing the script to only use
dialog in a terminal, instead of Xdialog.

I'm currently working with Mageia 3 x86_64, with all updates from
updates_testing.

CC: (none) => davidwhodgins

Comment 17 Thomas Spuhler 2013-11-27 18:33:25 CET
Any progress on this? It's still listed as NEW
Comment 18 Thomas Spuhler 2014-01-09 17:58:11 CET
Ping
This is bug hasn't died. It just doesn't look good if everytime you use a program, you see this bug popping up.
I am changing this to mga3 since I have no 32 bit cauldron installed and as far as I remember, last time I had one, the bug was fixed

Version: Cauldron => 3

Comment 19 Dimitrios Glentadakis 2014-03-06 16:43:07 CET
In Mageia 4 64bits, i didn't see yet any of these messages.
fixed ?
Comment 20 Thomas Spuhler 2014-03-06 18:27:38 CET
I think it's fixed an Mga4, 32 and 64 bit's

I don't have any mga3, 32 bit installed anymore (to check)
Comment 21 Morgan Leijström 2014-03-08 14:01:35 CET
I see this message starting Bricscad V14 from terminal in mga3-64 but not on my mga4-64 machine.

CC: (none) => fri

Comment 22 Thomas Spuhler 2014-04-12 01:58:23 CEST
This bug is now about one year old. So let's close it if we cannot fix it.

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 23 Dimitrios Glentadakis 2014-04-12 07:09:40 CEST
(In reply to Thomas Spuhler from comment #22)
> This bug is now about one year old. So let's close it if we cannot fix it.

... or let's leave it open (if it is still valid)
Comment 24 Barry Jackson 2014-04-13 12:37:50 CEST
I fixed the google droid part of this (hopefully) in October so this should not be happening in Mga4/5.
Comment 25 shiming zhou 2014-04-13 17:28:45 CEST
this bug seems not fixed  in mga4 64bit.This is the warnning message:
fontconfig warning: "/etc/fonts/conf.d/65-4-sazanami-mincho.conf", line 8: Having multiple values in <test> isn't supported and may not work as expected
Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-4-sazanami-mincho.conf", line 8: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-4-sazanami-gothic.conf", line 8: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-4-sazanami-mincho.conf", line 8: Having multiple values in <test> isn't supported and may not work as expected

CC: (none) => shimingzhou1980

shiming zhou 2014-04-13 17:29:14 CEST

Version: 3 => 4

Comment 26 Thomas Spuhler 2014-04-13 17:58:28 CEST
this looks to me as if it's not a fontconfig issue. Shouldn't we submit a new bug?
Comment 27 Marek Laane 2014-04-13 18:05:12 CEST
sazanamifonts part is reported as https://bugs.mageia.org/show_bug.cgi?id=11627

CC: (none) => bald


Note You need to log in before you can comment on or make changes to this bug.