After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 689254 - top panel font rendering (anti-alias) problem
top panel font rendering (anti-alias) problem
Status: RESOLVED INCOMPLETE
Product: gnome-shell
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-11-29 05:20 UTC by dujiulun2006
Modified: 2017-11-01 13:33 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot (127.79 KB, image/png)
2012-11-29 05:20 UTC, dujiulun2006 		Details

Description dujiulun2006 2012-11-29 05:20:11 UTC 
Created attachment 230154 [details]
Screenshot

I'm currently using GNOME Shell 3.6.2 with Arch Linux (x86), Intel Corporation Core Processor Integrated Graphics Controller (driver: i915 / don't know if relevant).

I have selected the anti-alias method in gnome-tweak-tool to be RGBA with subpixel order RGB. I tried grayscale and RGBA with different orders and RGB worked the best.

The font rendering worked all right for the whole system except in the top panel of GNOME shell. All the characters, especially the bold and the gray, have a red shade on the right side and a blue one on the left. It looks like using BGR order incorrectly. I'm using Faience theme but since there's no way to configure subpixel orders in theme CSS, it should not be the problem.

If I use a theme with a light top panel, the font there will look weird too. The same problem occurs when I was using Ubuntu 11.10/12.04/10 with Unity panel and a light color theme.
Comment 1 Allan Day 2015-02-26 23:33:03 UTC 
Sorry that no one has responded to this report sooner. Since it relates to such an old gnome-shell version, I have to ask whether it is still a problem in a more recent version (we are close to releasing 3.16; it would be great if you could test with 3.14 or 3.15.x). Thanks.
Comment 2 Alexandre Franke 2017-11-01 13:33:35 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!