My workaround worked for months without issues (at least for me): https://bugs.launchpad.net/ubuntu-font-family/+bug/744812/comments/81 After placing the conf file in the proper directory, the font cache must be refreshed to see the results (I use "fc-cache -fv" both as user and super-user). I used successfully this "technique" with other annoying fonts too, as Roboto ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733077#20 ) and Nimbus Sans ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645876#10 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645876#17 ). It's basically reassigning the wrong hard-coded font properties with the correct ones using fontconfig. If adding other fontconfig configuration files is not the preferred way, the other way I can only see is to edit the font properties directly into the ttf/otf files.
My workaround worked for months without issues (at least for me): /bugs.launchpad .net/ubuntu- font-family/ +bug/744812/ comments/ 81 /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 733077# 20 ) and Nimbus Sans ( http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 645876# 10 http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 645876# 17 ).
https:/
After placing the conf file in the proper directory, the font cache must be refreshed to see the results (I use "fc-cache -fv" both as user and super-user).
I used successfully this "technique" with other annoying fonts too, as Roboto ( https:/
It's basically reassigning the wrong hard-coded font properties with the correct ones using fontconfig. If adding other fontconfig configuration files is not the preferred way, the other way I can only see is to edit the font properties directly into the ttf/otf files.