Thanks for your input Gunnar, that might be really playing a role in the
problem.
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.
I doubt this is relevant — it was long ago and before any snap was used
by default — but I recall that when we started to use Noto fonts for CJK
languages in Xenial, there was initially an issue in Chrome/Chromium
where it used the wrong weight if the font file included multiple
weights (bug #15755
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/4iCv6KVjbNBYl
I installed ubuntu-fonts-classic from mantic on my lunar desktop (it's
not available for lunar). It removed ubuntu-fonts, but the fonts look ok
now in google docs. Got some differences in my desktop too, but still
looks ok.
--
You received this bug notification because you are a member of
Documen
Bold renders fine given simple CSS:
Ubuntu.
Ubuntu bold.
This looks specific to Google Docs.
** Attachment added: "fonts.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+attachment/5712423/+files/fonts.png
--
You received this bug notification because you
The new font relies on some different mechanism to determine the style
of a given typeface, as each different style points to a same file. The
old font doesn't do that. Maybe that could be tripping the resolution.
--->
# ubuntu-fonts
lrwxrwxrwx 1 root root 20 jun 21 10:35 UbuntuMono-B.ttf ->
'
Workaround:
apt install fonts-ubuntu- fonts-ubuntu-classic
--
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 displa
I can confirm this is still happening in mantic, using the following
versions:
chromium 118.0.5993.88
fonts-ubuntu 0.869-0ubuntu1
--
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/bu
Andreas noticed in the duplicate report that
> The chromium console log also shows a lot of these 404 errors for *.woff2
> fonts:
>
> GET
> filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2
> net::ERR_FILE_NOT_FOUND
--
You received this bug notific
** Tags added: lunar
--
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
** Description changed:
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
> 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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fonts-ubuntu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to fonts-ubuntu in Ubuntu.
https://bugs.launchp
13 matches
Mail list logo