← Back to team overview

documentation-packages team mailing list archive

[Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar

 

> One thing that may be relevant: if I force-refresh my test Google Doc
I see all four Ubuntu font lines initially being rendered as bold. The
light and medium lines are then re-rendered with the correct weight.
It's as if bold was the default weight and the normal variant
disappeared.

Interesting observation, I can reproduce that.

> As far as I can tell I was already running Chromium 112.0.5615.49 in
Kinetic, and with Chromium being a snap I don't quite understand why the
Ubuntu series would matter.

Because Ubuntu Lunar uses the 0.83-6ubuntu1 while older releases are
currently on the older 0.863-0ubuntu3.

-- 
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to fonts-ubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/2019045

Title:
  [snap] New Ubuntu font with normal weight displayed as bold in Google
  Docs in Chromium after upgrading to Lunar

Status in chromium-browser package in Ubuntu:
  Triaged
Status in fonts-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing a rendering regression after upgrading from Kinetic to Lunar.
  Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium.

  Printing is also affected, unless I use Google Docs' download to PDF
  function, although that probably triggers a server-side rendering.

  This issue does not occur in Firefox.

  One thing that may be relevant: if I force-refresh my test Google Doc
  I see all four Ubuntu font lines initially being rendered as bold. The
  light and medium lines are then re-rendered with the correct weight.
  It's as if bold was the default weight and the normal variant
  disappeared.

  As far as I can tell I was already running Chromium 112.0.5615.49 in
  Kinetic, and with Chromium being a snap I don't quite understand why
  the Ubuntu series would matter.

  I have also tried version 114.0.5735.16 (in latest/beta at the
  moment); the symptoms are identical.

  The attachments show the rendering error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions