Yesterdays fetchmsttfonts update borked my font rendering

Hi guys,

Yesterday there was an update to the msttfonts package, and it seems to have somehow borked my font rendering. Does anyone have any idea what could be wrong?

For font hinting, i use libfreetype6 from this repository: https://build.opensuse.org/project/show/home:nick31:INFINALITY-ULTIMATE and especially fonts in gtk apps look horrible.

Thanks.

openSUSE 13.2 w KDE

Well, you are not alone. I get mine from namtrac and as of yesterday they are awful

Mal

On 20/05/15 17:36, interele wrote:
>
> holden87;2711050 Wrote:
>> Hi guys,
>>
>> Yesterday there was an update to the msttfonts package, and it seems to
>> have somehow borked my font rendering. Does anyone have any idea what
>> could be wrong?
>>
>> For font hinting, i use libfreetype6 from this repository:
>> http://tinyurl.com/m7sl7xp and especially fonts in gtk apps look
>> horrible.
>>
>> Thanks.
>>
>> openSUSE 13.2 w KDE
>
> Well, you are not alone. I get mine from namtrac and as of yesterday
> they are awful
>
> Mal
>
>

One thing I find helpful is not install msfonts at all
However I use this repo though

http://download.opensuse.org/repositories/home:/nick31:/INFINALITY-ULTIMATE/openSUSE_13.2/

Well, I don’t have a problem here and didn’t notice any change.

But just to be clear: yesterday’s fetchmsttfonts update just removed a server (which doesn’t exist any more) from the list of mirrors that are tried to download the MS fonts.
That broken server might have prevented downloading the fonts at all.

So maybe you didn’t have the MS fonts installed at all, but they are now and that’s what caused the change? I.e. maybe they are used now instead of the fonts that have been used before…
Try to uninstall the package, I’d suggest.

And you can roll back
http://paste.opensuse.org/28133382

Yes, but I doubt that would help.

Again, the package has not really changed. And the package just downloads the fonts from a server and installs them.

On 2015-05-20 19:16, wolfi323 wrote:

> But just to be clear: yesterday’s fetchmsttfonts update just removed a
> server (which doesn’t exist any more) from the list of mirrors that are
> tried to download the MS fonts.
> That broken server might have prevented downloading the fonts at all.

Does that change trigger the script that does the actual downloading?
Because it is not necessary at all if the fonts are already installed.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Well, I got the update yesterday via zypper up and then watched as it proceeded to download and install a bunch of fonts. Whether all those fonts were actually installed previously, I cannot say with certainty (I believe they were), as I don’t fuss about fonts much. :wink: FWIW, I have no obvious issues with fonts today. I am on 12.3 64-bit KDE.

On 2015-05-20 21:36, JJMT wrote:

> Well, I got the update yesterday via zypper up and then watched as it
> proceeded to download and install a bunch of fonts. Whether all those
> fonts were actually installed previously, I cannot say with certainty (I
> believe they were), as I don’t fuss about fonts much. :wink: FWIW, I have no
> obvious issues with fonts today. I am on 12.3 64-bit KDE.

12.3? It is out of maintenance, EOL. How did you update that one?

Anyway, I updated two machines with 13.1 and I saw no issues.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Whilst the thread is titled ‘fetchmsttfonts etc’ I’m pretty sure it’s not that.
I update a second machine this morning as a test and the fonts in Chrome
and Vivaldi are noticeably ‘borked’

The first was 13.2 this is 13.1. The moral of the story is probably - stick
with the font rendering that comes with openSUSE.

I will investigate

M

Now isn’t this interesting…

Start Chrome with

google-chrome --force-device-scale-factor=1

and it all looks beautiful again. This may not
be the original posters problem but it seems
to be mine. Google says Chrome 43 has added
support for retina displays and the like.

How odd

M

Well, if I read the script correctly, it does so unconditionally, yes:

And that script is run on every install/update of that package I think, as it is installed to /var/adm/update-scripts/.
In case of yesterday’s update this was even intended/necessary… :wink:

Sorry. Typo. 13.2. :embarrassed: