Top bar w/ radiance theme shows ugly colored fringe (unity2D and, to a lesser extent, unity3D)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Unity |
New
|
Undecided
|
Unassigned | ||
| unity-2d (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
Context : 12.04 Precise, fresh install (details below).
Launch unity2D session. Default ambiance theme. Look at top bar. Nice subpixel antialiasing on text like everywhere.
Action : switch theme from ambiance to radiance
Expected : still nice subpixel antialiasing on text everywhere.
Observed : bright irrelevant colour fringe on text. Icons remain ok. Drop-down menus remain ok. All other text on screen remain ok. Only top bar default text is bad.
I made two screenshots exactly the same except theme change, with a *4 magnification of the menu part, to make it more obvious.
Detailed information :
Default radiance theme shows nicely antialiased text with subpixel optimization using subtle reddish/bluish colored fringes.
We've seen that for years and it works very well.
On 12.04 precise, switching from ambiance theme to radiance theme creates very saturated coloured fringes around text, including application name, clock, user name (but not top right icons like battery, wifi, gear).
Oddly enough, when clicking on a menu entry, the drop-down menu is correctly rendered and anti-aliased, and it also redraws over the menu name, which becomes nicely rendered, subpixel etc. The clicked menu stands out from its neighbors. Closing the menu brings the ugly rendering again.
It looks like antialias algorithm goes wrong, with very bright colors like cyan instead of subtle reddish/blueish . Math overflow ? Anyway, on clicking a menu the very same text becomes correct. Compare "Search" and "Terminal" in screenshot.
Tech information :
$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
Apt-get update & apt-get upgrade every few hours.
$ LC_ALL=C apt-cache policy unity-2d
unity-2d:
Installed: 5.8.0-0ubuntu1
Candidate: 5.8.0-0ubuntu1
Version table:
*** 5.8.0-0ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity-2d-panel 5.8.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
Date: Thu Apr 12 11:59:09 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120410)
ProcEnviron:
PATH=(custom, user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: unity-2d
UpgradeStatus: No upgrade log present (probably fresh install)
| Stéphane Gourichon (stephane-gourichon-lpad) wrote | #1 |
| Stéphane Gourichon (stephane-gourichon-lpad) wrote | #2 |
| summary: |
- Top bar w/ radiance theme shows ugly colored fringe + Top bar w/ radiance theme shows ugly colored fringe (unity2D and, to a + lessed extent, unity3D) |
| summary: |
Top bar w/ radiance theme shows ugly colored fringe (unity2D and, to a - lessed extent, unity3D) + lesser extent, unity3D) |
| Stéphane Gourichon (stephane-gourichon-lpad) wrote | #3 |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in unity-2d (Ubuntu): | |
| status: | New → Confirmed |
| Thomas Krause (krause) wrote | #5 |
| Thomas Krause (krause) wrote | #6 |
| Bartosz Radaczyński (radaczynski) wrote | #7 |
| Peter Mertz (frottier) wrote | #8 |
| Dom (d-o-m-e) wrote | #9 |
| Changed in unity-2d (Ubuntu): | |
| importance: | Undecided → Low |
| Adolfo Jayme Barrientos (fitojb) wrote | #10 |
Returning to Unity3D, the difference observed also exists there.
It is simply much less noticeable.
I made similar screenshots. Exact same description as above applies.
On the x4 zoomed area, one can see that the text always (whatever 2D/3D and theme) has *more contrasted* fringe than the dropdown menu title.
On the x4 zoomed area, radiance theme (bottom), one can see that the text always (whatever 2D/3D) has fringe that extends to the bottom, while the fringe on ambiance theme never expands to the bottom.
Is there some "carved in" rendering option enabled sometimes in the rendering engine ? That might be the triggering parameter.