Description of problem: Fontconfig warnings for google-droid fonts were repaired but fontconfig still spills over with warnings about sazanami fonts as following: 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 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedCC: (none) => dmorganec, puntogil, thierry.vignaud
*** Bug 12564 has been marked as a duplicate of this bug. ***
CC: (none) => ralgith
I think the approach as used in google-droid will probably fix this. I used a patch for google-droid so it could be simply removed if it broke anything. I have not seen any reports of breakage on that package, so it's probably better to apply the changes directly to the .conf files for this one.
CC: (none) => zen25000
Still prominently present
Fixed in sazanami-fonts-0.20040629-22.mga5 Please test and re-open if there are any issues. Closing as fixed.
Status: NEW => RESOLVEDResolution: (none) => FIXED
One warning down, one yet to go, I'd say: 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
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
(In reply to Marek Laane from comment #5) > One warning down, one yet to go, I'd say: > 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 Oops - missed that one - should be fixed in sazanami-fonts-0.20040629-23.mga5 Thanks for testing!
Closing - again :)
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Seems to be OK now. Many thanks for resolving this harmless but annoying bug!
*** Bug 7743 has been marked as a duplicate of this bug. ***
CC: (none) => balcaen.john