Version: (using KDE 4.3.1) OS: Linux Installed from: Ubuntu Packages Reported originally in Launchpad at https://bugs.launchpad.net/bugs/377552. ------------------------ Ever since I upgraded to KDE 4.3 beta on my Karmic system, the icon titles in Kickoff have been displayed using grayscale anti-aliasing instead of subpixel rendering. The descriptions (smaller, gray text) and the title at the top are properly drawn using subpixel rendering. I have attached a screenshot to demonstrate. screenshot link: http://launchpadlibrarian.net/26854763/nosubpixel.png ------------------------- The Lancelot widget is correctly rendering the text we noticed. This was even confirmed with users of other distros on IRC as well. I can't check my trunk build as it is currently on the fritz.
it is using Qt to do the font rendering: p.drawText(titleRect, Qt::AlignLeft|Qt::AlignVCenter, titleText); it's not something plasma does special.
The Task Manager and Folder View widget on Kubuntu also use grayscale, but the Digital Clock and Calculator have lcd-antialiased font. Maybe they use a different method for drawing text?
(In reply to comment #2) > The Task Manager and Folder View widget on Kubuntu also use grayscale, but the > Digital Clock and Calculator have lcd-antialiased font. > > Maybe they use a different method for drawing text? I confirm these bugs in OpenSuSE 11.1, KDE 4.3.3 Maybe this affects font rendering? http://websvn.kde.org/branches/KDE/4.3/kdebase/workspace/plasma/applets/kickoff/ui/urlitemview.cpp?view=markup 147 painter->setRenderHint(QPainter::Antialiasing, false);
Bug still occurs in openSUSE 11.3 Milestone 6. Qt: 4.6.2 KDE: 4.4.2 Kickoff menu has missing subpixel hinting (when enabled). Main categories are fine but all apps and their categories NOT. Why this bug is set to 'RESOLVED as WONTFIX' while it's not resolved? Regards, Mariusz
Created attachment 43115 [details] kickoff menu with enabled subpixel hinting but text is rendered incorrectly
This is still an issue in KDE 4.4.2 (Kubuntu Lucid Lynx 10.04 x64). Since this bug is marked as RESOLVED/WONTFIX, would someone advise if we need to open a new bug for this issue?