I wanted to enable nice looking fonts in KDE a while ago and went into my OpenSuse and brought up the Fonts options * I mark "Use anti-aliasing" as "Enabled" and click Configure... * I uncheck "Exclude range" because I want small fonts also anti-aliased * I check "Use sub-pixel rendering" and use the default "RGB" mode * Hinting style is changed to "Slight" because it makes it easier to read text for long periods of time (at work) for me Now when I use Konsole it has some very subtle re-draw issues and artifacts. There are two problems: 1.) When typing its clear the "line height" or something isn't expecting something to be drawn outside of some bounds. Basically it drops the lower portions of some letters like "g" and "p" as the screen is re-drawing while you type. 2.) When scrolling the portions that appear to be clipped in (1) are not cleared sometimes and artifacts are left on the screen. This is in the screenshot attached to this bug: http://i.imgur.com/YAY28EW.png (Notice random green spec at the bottom of the screenshot) Note: Triggering Konsole to re-draw in some scenarios makes these artifacts go away, and getting a screenshot can be difficult. Everytime you take a screenshot the artifacts will go away. Reproducible: Always Steps to Reproduce: 1. Enable font anti-aliasing in KDE 2. Enable sub-pixel rendering (may be optional) 3. Launch Konsole and type looking at lower portions of your letters and how they redraw 4.) Try `'ls -lh` a directory with some scrolling and see the artifacts as in the screenshot Actual Results: Green pixel artifacts or whatever your foreground terminal color is Expected Results: Should have terminal text and background with no artifacts. I like turtles. I don't run anything but pretty standard OpenSUSE 12.3 - this is a work machine
Does it happen with every font? Also, please try increasing the Line Spacing in Konsole profile setting's "Advanced" tab. It is possible that the font simply reports wrong information about the number of pixels it needs.
I have tried it with two fonts that did the same thing: * Stock OpenSuse font(Liberation Sans (8px) * Droid Sans Mono (10px) Thanks for letting me know about the Line Spacing option I bumped that up to 2 and haven't seen the bug since. It's also nice because I was wanting exactly that for basic readability (I try to keep things very simple) I will report back if I see the graphics glitch with the line spacing, otherwise that's a good work around for a subtle problem.
Line spacing appears to solve it! Haven't had the problem since and I worked all day yesterday while on this machine. Thanks again, Kris