← 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


Thanks for your input Gunnar, that might be really playing a role in the

After all, it turns out the error Andreas reported is also present when
the behavior is correct, i.e. with ubuntu-fonts-classic I get

Failed to get origin+type directory: { uri: filesystem:https://docs.google.com/persistent/docs/fonts/4iCs6KVjbNBYlgo6fQ.woff2, storage key: { origin: https://docs.google.com, top-level site: https://google.com, nonce: <null>, ancestor chain bit: Same-Site } } error:-4

** Changed in: chromium-browser (Ubuntu)
   Importance: Medium => Low

You received this bug notification because you are a member of
Documentation Packages, which is subscribed to fonts-ubuntu in Ubuntu.

  [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:
Status in fonts-ubuntu package in Ubuntu:

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 or Google Chrome.

  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

  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: