LinuxQuestions.org Member Success StoriesJust spent four hours configuring your favorite program? Just figured out a Linux problem that has been stumping you for months?
Post your Linux Success Stories here.
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.
When I look through my Xorg.0.log file it shows that it's loading freetype from /usr/X11R6
This is obviously incorrect as I compiled freetype into /usr/lib
Perhaps Xorg comes with it's own version of freetype?
I changed the symlink in X11R6 to point to the proper one in /usr/lib hopeing that would fix things.
Xorg.0.log now shows:
(EE) LoadModule: Module freetype does not have a freetypeModuleData data object.(II) UnloadModule: "freetype"
(II) Unloading /usr/X11R6/lib/modules/fonts/libfreetype.so
(EE) Failed to load module "freetype" (invalid module, 0)
On a side note, after completing Franklin's steps xfsinfo no longer works, neither does xselfont.
I've commented out unix:/7100 from xorg.conf and made sure to complete all the obvious other steps.
I'm still dealing with antialiased blurry fonts. many hours into this, anyone able to offer some suggestions?
After following Frank's HOWTO and hint on OpenOffice, I still cannot make OpenOffice fonts look readable.
I have Verdana 7 on all (most of) my applications (GTK2 mainly). OpenOffice only fails to comply. Antialiased fonts are OK, but it becomes horribly slow - almost unusable - for my machine. Thus, I disabled the anti-aliasing in OpenOffice. I enabled system fonts for user interface.
So, the result is that OpenOffice 2.0 has menus and toolbars with normal, desktop-wide fonts. They look quite acceptable, as in any other program. But the actual text (the text to be edited) looks bad. Exactly as their entire help stuff. It gave the same results before recompiling freetype. I have the feeling that it does font renderring itself, without BYTE_CODE_INTERPRETER.
My question: how can I make OpenOffice comply with the system/desktop-wide settings and use BYTE_CODE_INTERPRETER for rendering fonts?
After following Frank's So, the result is that OpenOffice 2.0 has menus and toolbars with normal, desktop-wide fonts. They look quite acceptable, as in any other program. But the actual text (the text to be edited) looks bad. Exactly as their entire help stuff. It gave the same results before recompiling freetype. I have the feeling that it does font renderring itself, without BYTE_CODE_INTERPRETER.
My question: how can I make OpenOffice comply with the system/desktop-wide settings and use BYTE_CODE_INTERPRETER for rendering fonts?
yes it does, and this is supposed to solve it:
LD_PRELOAD="/usr/lib/libfreetype.so" sofice
However, I have extremely rarely successfully compiled app from sources, and never applied patches. (Guess patches require source and cannot be used on .deb package?) and OpenOffice is probably going to give some error when compiling, not for beginner like me.
From the last link you provided, this problem is supposed to be fixed with OOo 2.0.3. Don't try to compile. I really doubt it would. However, never tried. Anyway, you'd need about 4-6 GB of spare space.
--update: I have just checked OOo 2.0.3. No word about libfreetype in the ChangeLog. Maybe in 2.0.4?
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,634
Rep:
Quote:
Originally Posted by Franklin
Hi again. Sorry this took so long - I was away for a while and returned to too much work.
I posted some new screenshots that are meant to show the Firefox, Mozilla, and Konqueror browsers with the font configurations
that I use. This is nothing you couldn't arrive at easily through trial and error, but since I was asked - here it is:
You don't have permission to access /vze8992v/ on this server.
Can you repair that?
In case I have not said so before, I use your HowTo since I don't know when and have it even copied to my "manual" for re-installations. So: Thank you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.