[SOLVED] Problem with fonts after last current upgrade.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As you can see, the "P" is worse, but the "N" is better. I think the hinting engine is not the issue, but rather the bounding box, which makes sense given my quick reading the patch that's been linked in this thread.
This still doesn't fix it for me. I created this file then restarted X and Firefox, still see the problems I had before. I tried with and without the previously-discussed changes to /etc/profile.d/freetype.sh.
Ponce already mentioned this, but if you read the mailing lists, these problem are caused by freetype's new subpixel rendering technique called harmony. Programs using the skia graphics library (firefox for example) are affected. Most programs have fixes upstream, so we will just have to wait for newer versions to come out or downgrade to freetype 2.8
Slackware-current downgraded from freetype-2.8.1-x86_64-1 to freetype-2.8-x86_64-1. This avoids the issue for now. It's working fine for me. Thanks for the quick response; the bad text was driving me nuts!
After I set it, I launch xfce from sddm (from ktown), I launch a terminal, and check whether it's set. It's not. I'm going to try to check why not later tonight.
As for this...
It's because I'm using FISH, and FISH doesn't source /etc/profile or /etc/profile.d.
I ended up putting the following in /etc/fish/config.fish:
I have set
Use anti-aliasing: Enabled
sub-pixel rendering type: RGB
Hinting style: Slight
Are you using Xfce? I was able to bypass the problem by using those settings also, but if recompile the freetype source with subpixel rendering then the problem occurred. Also the problem occurred for me in Mate regardless of my compile options. If you read the mailing list it sheds more light on exactly what the cause is. I am just glossing over the details.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.