documentation-packages team mailing list archive
Mailing list archive
[Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
Same behaviour in current Bionic installs (package version is the same
** Tags added: artful bionic
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-font-family-
sources in Ubuntu.
"Ubuntu Light" font has heavier weight than "Ubuntu"
Status in One Hundred Papercuts:
Status in Ubuntu Font Family:
Status in ubuntu-font-family-sources package in Ubuntu:
Status in ubuntu-font-family-sources source package in Wily:
After upgrading from Vivid to Wily, pages using the "Ubuntu light" font actually renders with a weight heavier than the regular one in web pages.
This happens with Chrome/Chromium and also the Ubuntu browser.
After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in
place of 0.83-0ubuntu1), the issue is fixed.
See the attached screenshot showing the result seen browing
DistroRelease: Ubuntu 15.10
Package: ttf-ubuntu-font-family 0.83-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
Date: Sun Nov 1 17:55:19 2015
InstallationDate: Installed on 2014-10-14 (382 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago)
IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users
which impacts the usability and visual design.
The new version of font package (0.831) corrects the relationship
between Light and Medium weight to follow the commonly used naming
Ubuntu Light Light Light Italic
Ubuntu Regular Italic Bold Bold Italic
Ubuntu Medium Medium Medium Italic
Ubuntu Condensed Regular
Ubuntu Mono Regular Italic Bold Bold Italic
TEST CASE: in 15.10, go to
If the Light weight renders heavier than Normal weight, the bug is in
0.831 was tested by manually running in 15.10 and no regression was
noticed, while the bug was fixed. The potential for regression is
To manage notifications about this bug go to: