FS#26624 - [kdebase-konsole] qt 4.8 breaks some font rendering

Attached to Project: Arch Linux
Opened by Pierre Schmitz (Pierre) - Wednesday, 26 October 2011, 07:36 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 31 March 2012, 07:06 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ronald van Haren (pressh)
Andrea Scarpino (BaSh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

I noticed that the font rendering with that release candidate of QT is broken. Especially characters like q, p and g are cut off at the bottom. This seems to happen when using the intel or nouveau driver but not nvidia.

How to reproduce:
* Use intel or nouveau driver
* Use terminus-font in konsole
* Type in characters as q, g, p

A Donwgrade to Qt 4.7 "foxes" the issue.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Saturday, 31 March 2012, 07:06 GMT
Reason for closing:  Fixed
Additional comments about closing:  kdebase-konsole 4.8.2-2
Comment by Andrea Scarpino (BaSh) - Wednesday, 26 October 2011, 07:37 GMT
Pierre can you provide any screen? Everything seems ok here, and I'm using an Intel card.
Comment by Усиков Владимир (Behem0th) - Wednesday, 26 October 2011, 17:58 GMT
Сonfirm for terminus-font in Konsole and Yakuake.
   fonts_qt_4.8.png (237.7 KiB)
Comment by Сковорода Никита (ChALkeR) - Wednesday, 26 October 2011, 22:20 GMT
I can reproduce this on Qt 4.8.rc1 from [testing].
Didn't try on 4.7.

OpenGL renderer string: Gallium 0.4 on AMD RS880
Konsole.
Konsole colorscheme: dark pastel (on screenshot), any other, it does not depend on colorscheme.
Text: «[chalker@pc ~]$ qgp = QGP».

«Bad» fonts: Terminus 11 (on screenshot), Terminus 11 bold, Terminus 9,12,14 (amount of cut-off slightly depends on font size), Terminal [DEC] 11, Terminal [Bitstream] 14, LucidaTypewriter 11,13 («g» has the end slightly cut off), FreeMono 10,11 (this bug might not be the case, letters are not cut off, but selection misplaces characters a bit),

«Fine» fonts: LiberationMono 9,11,12, Droid Sans Mono 9,10,11, DejaVu Sans Mono 9,10,11,12, Monospace 9,10,11,12, LucidaWriter 14 (yes, it looks ok on size 14).

   159.png (28.2 KiB)
Comment by Сковорода Никита (ChALkeR) - Wednesday, 26 October 2011, 22:28 GMT
By the way, i can't reproduce this in Kate for any of those fonts.
Comment by Сковорода Никита (ChALkeR) - Wednesday, 26 October 2011, 22:37 GMT
Also, shouldn't this be reported in KDE bug tracker instead?
Most probably this is KDE (Konsole) bug, but if they are sure that the code works as it should, then this most probably is Qt bug.

This looks like a minor bug to me (simple workaround: change font to any of listed in «Fine» row).
Comment by Andrea Scarpino (BaSh) - Sunday, 30 October 2011, 10:18 GMT
Found the qt bug report https://bugreports.qt.nokia.com/browse/QTBUG-22270
Comment by Andrea Scarpino (BaSh) - Sunday, 30 October 2011, 10:21 GMT
and KDE one https://bugs.kde.org/show_bug.cgi?id=280896
Comment by Alessio Biancalana (dottorblaster) - Saturday, 05 November 2011, 10:20 GMT
Monaco has the same issue on Konsole.
I can confirm.
Comment by Andrea Scarpino (BaSh) - Monday, 19 December 2011, 20:37 GMT
Pierre confirmed the bug is still present in qt 4.8.0.

Anyway, if you enable "Enable Bi-Directional text rendering" in Konsole->Settings->Manage Profiles->Advanced the bug goes away.
Comment by Alessio Biancalana (dottorblaster) - Monday, 19 December 2011, 20:56 GMT
I'll test the behaviour.

I activated the option for bi-directional rendering but there wasn't any change, even after rebooting my machine.

EDIT - Terminus with Bi-Di option looks fine. Monaco doesn't.
Comment by Andrea Scarpino (BaSh) - Tuesday, 20 December 2011, 10:56 GMT
I cannot reproduce with both monaco and terminus.
   terminus.png (75.1 KiB)
   monaco.png (82.9 KiB)
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 20 December 2011, 16:10 GMT
Cannot reproduce using qt 4.8, kde 4.7, radeon driver. Fonts tested: dejavu, tamsyn mensch.
Comment by Marcus D. Hanwell (cryos) - Wednesday, 21 December 2011, 21:51 GMT
I am seeing this after updating to Qt 4.8.0 in KDE 4.7. Using Terminus 9 and I get fonts cut off, with the latest nVidia driver. It looks pretty ugly, bottom of several letters is cut off.
Comment by Marcin (emate) - Thursday, 22 December 2011, 10:51 GMT
Same issue here.
Qt: 4.8.0
KDE Development Platform: 4.7.4
Fonts tested: Clean, Terminus, Fixed.
Comment by Ivan Koryabkin (apathism) - Thursday, 22 December 2011, 20:57 GMT
This issue affects me too.

Also I noticed that font rendering in some KDE applications is different.
On the screenshot there are krunner working processes window (right)
and ksysguard processes (left). In the krunner fonts looks ugly due to
unbalanced letter spaces, but in ksysguard they are normal (just like
system-wide).

Arch: x86-64
Qt: 4.8.0
KDE: 4.7.4

/* Sorry for my English */

UPD:  FS#27674 
   screen.png (158.8 KiB)
Comment by Scott G (axanon) - Wednesday, 28 December 2011, 21:43 GMT
I use proprietary nVidia drivers and had this problem with Terminus. Using bi-directional text rendering did work around the problem for me.
Comment by Marcin (emate) - Friday, 30 December 2011, 08:53 GMT
Indeed, enabling bi-directional text did the trick. Thanks.
Comment by Andrea Scarpino (BaSh) - Wednesday, 28 March 2012, 19:29 GMT
Is this fixed? If isn't, please try qt 4.8.1-1 and let me know.
Comment by Ivan Koryabkin (apathism) - Thursday, 29 March 2012, 17:14 GMT
Still works with this issue for me. :(
Comment by Pierre Schmitz (Pierre) - Thursday, 29 March 2012, 17:55 GMT
And to make it clear: this issue still exists and the workaround introduces other rendering issues. And as upstream already closed thise bug for no reason they are probably not interested in fixing it anyway.
Comment by Jekyll Wu (adaptee) - Thursday, 29 March 2012, 18:10 GMT
"the workaround introduces other rendering issues."

You are welcome to open another report for those rendering issures on bugs.kde.org.

"as upstream already closed thise bug for no reason they are probably not interested in fixing it anyway."

Which upstream report are you talking about? URL please.

https://bugs.kde.org/show_bug.cgi?id=280896 is still open, although a dirty fix has been pushed onto the master branch.

Loading...