documentation-packages team mailing list archive

[Nathan Teodosio <2019045@xxxxxxxxxxxxxxxxxx>]

More information dump:

* It's easier to see the error Andreas mentioned with --enable-
logging=stderr:

--->
[246126:246235:1023/123348.818876:WARNING:obfuscated_file_util.cc(1323)] Failed to get origin+type directory: { uri: filesystem:https://docs.google.com/persistent/docs/fonts/4iCv6KVjbNBYlgoCxCvTsg.woff2, storage key: { origin: https://docs.google.com, top-level site: https://google.com, nonce: <null>, ancestor chain bit: Same-Site } } error:-4
[246126:246235:1023/123348.818941:WARNING:obfuscated_file_util.cc(1323)] Failed to get origin+type directory: { uri: filesystem:https://docs.google.com/persistent/docs/fonts/4iCp6KVjbNBYlgoKejZPsmyN.woff2, storage key: { origin: https://docs.google.com, top-level site: https://google.com, nonce: <null>, ancestor chain bit: Same-Site } } error:-4
<---

I don't quite understand the process there, an uneducated guess: It is
trying to fetch a font and then storing it using the filesystem API —
which would save it in snap/chromium/common/chromium/Default/File\
Systems but that directory doesn't even exist. Maybe Firefox's
implementation differs from Chromium's critically enough to hit this
bug. Disabling that with --disable-file-system has no effect.

* Docs uses a remote font instead of a system font because --disable-
remote-fonts prevents the Ubuntu font from loading despite it still
being listed (the 't' character is a giveaway). This is in line with the
error message.

* Since we don't get the problem in Firefox, I tried switching the user
agent to Firefox just to see if behavior changed; it didn't.

-- 
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 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
  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