You are not logged in.
Hello,
The package freetype2 2.6.4-2 (testing) is not available hinting management. After update hinting does not work.
Fonts look terrible - blurry , fatty.
Offline
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Mod note: Moving to Testing.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
freetype2 2.6.4-2 is now on stable repo and the bug is still here : ugly fonts, the fonts are too bold,
I have to downgrade to 2.6.3-1 version as workaround
Last edited by Potomac (2016-07-07 04:06:13)
Offline
Hello,
with freetype2-2.6.4-2 there is a bug : fonts are too bold, they look terrible, blurry , fatty
hinting doesn't seem to work with this version,
I tried the avalaible settings in /etc/environment :
FT2_SUBPIXEL_HINTING=0 # Classic mode
FT2_SUBPIXEL_HINTING=1 # Infinality mode
FT2_SUBPIXEL_HINTING=2 # Default mode
but it doesn't fix the problem, fonts are still ugly ( too bold, for example in gimp, thunderbird, web sites in firefox ),
with the previous version ( freetype2 2.6.3-1 ) there is no problem
Offline
Merged similar topics
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
@ewaller : you should put this thread in the section "Pacman & Package Upgrade Issues",
because freetype2 2.6.4-2 is now on "extra" repo, and not on testing repo
Last edited by Potomac (2016-07-07 04:17:42)
Offline
Thank you. Moving. You should use the report link in the future.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I have not try yet, my plan is to install Arch later today.
I just read this bug report:
https://bugs.archlinux.org/task/49981
@ewaller : you should put this thread in the section "Pacman & Package Upgrade Issues",
because freetype2 2.6.4-2 is now on "extra" repo, and not on testing repo
EDIT: Sorry wrong thread but same topic.
Last edited by Nordicruler (2016-07-07 04:31:10)
The world is going to an end, Please log off!!
Offline
I've exported FT2_SUBPIXEL_HINTING=0 in my /etc/profile.d/extras.sh and it seems to do the trick. On the other hand upstream changing defaults to something that looks worse is kind of annoying, just like what happened with fontconfig's default hinting style.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
I downloaded a previous version of freetype2 from https://archive.archlinux.org/packages/f/freetype2/ and installed it with pacman -U freetype2-2.6.3-1-x86_64.pkg.tar.xz and had nice looking fonts back.
Offline
I concur that freetype2 2.6.4-2 is broken, had to downgrade to freetype2 2.6.3-1 as well. The bug report has been closed on account of "not a bug but configuration issue". I do not think that is correct as the 3 config options do not seem to work and produce the same problem albeit in varying degrees. So it does look like a bug, either with the 3 patches applied to arch freetype2 package in latest version or upstream.... I'd comment on the bug report but cannot at the moment, just registered with bugtracker but it does not recognize my user name yet.
Offline
@R00KIE, Thanks for the hint. Exporting FT2_SUBPIXEL_HINTING=0 in /etc/profile.d/extras.sh worked for me too.
Speak your mind even if your voice shakes.
Offline
@ROOKIE Exporting FT2_SUBPIXEL_HINTING=0 in /etc/profile.d/extras.sh works for me as well. Thank you!
Any chance you can post a link to a reference for this fix?
Offline
The post-install message tells you so. If you just go ahead and add all three lines it mentions you will overwrite your definitions with the last value which will be the new behaviour, you are only supposed to set just one of the three possible lines. If you did that, then there are chances that /etc/environment wasn't being parsed by your login shell, but profile.d is.
Offline
The post-install message tells you so. If you just go ahead and add all three lines it mentions you will overwrite your definitions with the last value which will be the new behaviour, you are only supposed to set just one of the three possible lines. If you did that, then there are chances that /etc/environment wasn't being parsed by your login shell, but profile.d is.
I was not referring to the post install message, I had tried both /etc/environment and ~/.pam_environment without success. Evidently those were not being parsed automatically by my login shell....
I was referring to using "extras.sh" in /etc/profile.d/
Not important...there's plenty of ways to export that value upon login, TBO.
Last edited by stef_204 (2016-07-07 14:54:48)
Offline
The environment files are read by pam_env, which should be part of /etc/pam.d/system-login .
Offline
My pacman logs tell me that in late 2014 (21st of December) truetype2 was upgraded to version 0.9.37-1. With it came a log message that said "Subpixel hinting can be enabled by adding FT2_SUBPIXEL_HINTING=1 to your environment". Does any one know why we seem to be getting this functionality again/back?
Offline
@ROOKIE Exporting FT2_SUBPIXEL_HINTING=0 in /etc/profile.d/extras.sh works for me as well. Thank you!
Any chance you can post a link to a reference for this fix?
No link I'm afraid, that file is where I export misc stuff I want to be set in my environment. You could call it fix-for-stuff-that-annoys-me.sh and it should still work, that is the idea behind the files in profile.d, they should be sourced when you login.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Just wanted to add that uninstalling the AUR "sharpfonts" package also fixes this, except then fonts go blurry (i.e. antialiased at small font sizes.) Reinstalling sharpfonts makes the fonts look ugly again, but setting FT2_SUBPIXEL_HINTING=0 fixes the problem.
It looks like the latest freetype is converting the subpixels into full black pixels, when antialiasing is switched off. Has anyone reported this bug upstream?
Offline
I tried the avalaible settings in /etc/environment :
FT2_SUBPIXEL_HINTING=0 # Classic mode
FT2_SUBPIXEL_HINTING=1 # Infinality mode
FT2_SUBPIXEL_HINTING=2 # Default modebut it doesn't fix the problem
I tried the alternative /etc/profile.d/ but that doesn't fix everything. The following however worked across the board:
echo 'FT2_SUBPIXEL_HINTING DEFAULT=0' >> /etc/security/pam_env.conf
Offline
I also had this problem, and got it solved, but I don't know if the process will work for anyone (BTW I do not use subpixel hinting, as I still use a CRT monitor). What I did was:
1. Backed up /etc/fonts/conf.d and then deleted it.
2. Re-installed latest freetype2 and fontconfig packages.
3. Deleted /etc/fonts/conf.d 10-hinting-slight.conf symlink.
4. Created a symlink to /etc/fonts/conf.avail/10-hinting-full.conf inside /etc/fonts/conf.d
5. As everything worked, I deleted the backup done on step 1.
If anyone tries this, please report if it works.
Last edited by doragasu (2016-07-09 17:22:40)
Offline
Exporting FT2_SUBPIXEL_HINTING=0 (I opted for /etc/profile.d/freetype2.sh) mostly worked for me.
I say mostly, because it worked for some applications (Firefox, HexChat, Rhythmbox, Vim, Gnome Tweak Tool) but not for others (Gnome Files/Nautilus, Gnome Terminal).
Also, unless I set gfx.font_rendering.fontconfig.fontlist.enabled to false on Firefox, some fonts (visible on Facebook or http://www.lemonde.fr/ ) are blurry and too bold. I don't think it's related to the present bug as I had this issue way before the freetype update, but I feel like something is wrong in the way (Arch?)Linux handles font rendering.
Last edited by monsieur moche (2016-07-09 21:15:21)
Offline
@monsieur moche
Search the forums for problems with fontconfig, you may be having problems with the change in the hinting default.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
my personnal font.conf file in ~/.config/fontconfig :
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target="font">
<edit mode="assign" name="rgba">
<const>rgb</const>
</edit>
</match>
<match target="font">
<edit mode="assign" name="hinting">
<bool>true</bool>
</edit>
</match>
<match target="font">
<edit mode="assign" name="hintstyle">
<const>hintfull</const>
</edit>
</match>
<match target="font">
<edit mode="assign" name="antialias">
<bool>true</bool>
</edit>
</match>
<match target="font">
<edit mode="assign" name="lcdfilter">
<const>lcddefault</const>
</edit>
</match>
<!-- Reject bitmap fonts -->
<selectfont>
<rejectfont>
<pattern>
<patelt name="scalable">
<bool>false</bool>
</patelt>
</pattern>
</rejectfont>
</selectfont>
<dir>~/.fonts</dir>
<alias binding="same">
<family>Helvetica</family>
<accept>
<family>Liberation Sans</family>
</accept>
</alias>
<alias binding="same">
<family>Times</family>
<accept>
<family>Liberation Serif</family>
</accept>
</alias>
</fontconfig>
with "FT2_SUBPIXEL_HINTING=0" setting in /etc/environment the results are almost good, but it's not as good as freetype 2.6.3 version, some fonts are a little too bold, but to see the difference between 2.6.4 and 2.6.3 version the user must have a very good eye and a good LCD screen
Last edited by Potomac (2016-07-10 16:22:01)
Offline