This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2108245 - Characters not showing up correctly in npm
Summary: Characters not showing up correctly in npm
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nodejs
Version: 9.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Zuzana Svetlikova
QA Contact: Jan Houska
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-18 16:55 UTC by Lukas Magauer
Modified: 2023-09-20 15:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 15:07:52 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
RHEL 9.0 showing unicode-table.com with missing characters (157.70 KB, image/png)
2022-07-18 16:55 UTC, Lukas Magauer
no flags Details
gfx.downloadable_fonts.enabled = true (385.09 KB, image/png)
2022-07-25 09:28 UTC, Akira TAGOH
no flags Details
gfx.downloadable_fonts.enabled = false (395.54 KB, image/png)
2022-07-25 09:31 UTC, Akira TAGOH
no flags Details
Picture from right after the first boot and browser start (126.23 KB, image/png)
2022-07-25 19:55 UTC, Lukas Magauer
no flags Details
Firefox with open dev tools (337.60 KB, image/png)
2022-07-25 19:59 UTC, Lukas Magauer
no flags Details
Screenshot from the npm install nodejs with the missing characters (8.72 KB, image/png)
2022-07-25 20:05 UTC, Lukas Magauer
no flags Details
another screenshot for woff2 (739.46 KB, image/png)
2022-07-26 04:06 UTC, Akira TAGOH
no flags Details
Firefox with open dev tools network tab (188.43 KB, image/png)
2022-07-27 19:23 UTC, Lukas Magauer
no flags Details
List of installed packages with font in the name (2.04 KB, text/plain)
2022-09-26 17:16 UTC, Lukas Magauer
no flags Details
Today's dnf update which fixed the problem for npm (14.46 KB, text/plain)
2022-09-26 17:17 UTC, Lukas Magauer
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5491 0 None Migrated None 2023-09-20 15:07:49 UTC
Red Hat Issue Tracker RHELPLAN-128061 0 None None None 2022-07-18 17:09:41 UTC

Description Lukas Magauer 2022-07-18 16:55:10 UTC
Created attachment 1897961 [details]
RHEL 9.0 showing unicode-table.com with missing characters

Description of problem:
We noticed some missing characters throughout the OS while browsing the web and also when using npm in GNOME Terminal.
I was testing with both Graphical Server and Workstation installs and both show the same behavior of missing characters (showing placeholder characters).
This was checked with a fully patched RHEL 9.0 system, with both Xorg and Wayland.
Also further this was tested both on a hardware system with the proprietory NVIDIA driver, as well as in a VMware ESXi environment as a VM.
For comparison I tested this on a fully patched Fedora Workstation 36 installation, which shows the characters just fine.

How reproducible:
always

Steps to Reproduce:
1. Install a Graphical Server or Workstation installation
2. Open the browser and visit the page https://unicode-table.com/en/blocks/supplemental-punctuation

Actual results:
You will see many placeholder characters (please look at the attached screenshot)

Expected results:
All characters showing up correctly

Additional info:
This was initially brought to our attention in Rocky Linux 9.0,
am also tracking this here: https://bugs.rockylinux.org/view.php?id=149

Thank you very much for your help in advance and if any information is missing I will gladly provide it!

Comment 1 Lukas Magauer 2022-07-18 16:58:59 UTC
P.S. I'm sorry if I got the wrong package, it was just a wild guess from where this issue might come from.

Comment 2 Caolan McNamara 2022-07-18 19:13:57 UTC
its definitely not libfonts which is quite an obscure java-only package used by an equally obscure java component eventually only used by the reporting engine in LibreOffice. Its probably not fontconfig either, but that's more plausible at least. Maybe there just isn't any fonts installed which can render the glyphs.

Comment 3 Lukas Magauer 2022-07-19 05:33:29 UTC
Interesting facts! Thank you for redirecting though!

Comment 4 Akira TAGOH 2022-07-22 11:14:56 UTC
No, not fontconfig either. but there are no fonts installed which has a coverage to render them right. However, speaking of that site, they expect to download and use woff2 even if you don't have a font. That may just takes a bit of time to finish downloading woff2. you'll see those is rendered properly at the end.

Comment 5 Lukas Magauer 2022-07-23 18:38:25 UTC
I looked at the downloads of the website very close now and what font should be used for these characters,
to me it looks like there are other parts of the website, where the font comes from either remote ttf or woff2 files, but not for these, it directly picks up the default font from the browser/OS.
On my Fedora 36 machine it says that it uses Noto Serif.

Furthermore I also mentioned that these characters are also missing if you are using npm, you just need to do a "dnf install npm" and then "npm install nodejs", you should see the download bar with these characters for short.

Comment 6 Akira TAGOH 2022-07-25 09:28:54 UTC
Created attachment 1899158 [details]
gfx.downloadable_fonts.enabled = true

I assume you use firefox. you may disabled web fonts support there. attached screenshot has been taken with gfx.downloadable_fonts.enabled = true. as you can see, the font being used for rendering is something not installed on the system.

Comment 7 Akira TAGOH 2022-07-25 09:31:05 UTC
Created attachment 1899159 [details]
gfx.downloadable_fonts.enabled = false

This is with gfx.downloadable_fonts.enabled = false. as you said, Noto Serif was used for rendering.

Comment 8 Akira TAGOH 2022-07-25 09:40:45 UTC
For npm, if the rendering of those characters affects functionalities in npm, npm should has dependencies to proper font package.

As a result, the problem is that fonts to rendering those characters is just missing on the system, but I don't think we should have them as a part of default fonts. I'll reassign this to npm if there are no objections.

Comment 9 Lukas Magauer 2022-07-25 19:55:35 UTC
Created attachment 1899255 [details]
Picture from right after the first boot and browser start

I wasn't trusting myself anymore now... So I just deployed a new system with the Workstation base environment,
right after the first booting I started the preinstalled Firefox and opened the page.
This screenshot is from exactly that moment

Comment 10 Lukas Magauer 2022-07-25 19:59:02 UTC
Created attachment 1899256 [details]
Firefox with open dev tools

Here is another screenshot with the Dev tools visible.

Comment 11 Lukas Magauer 2022-07-25 20:00:03 UTC
The gfx.downloadable_fonts.enabled parameter is by default set to true as far as I can see.

Comment 12 Lukas Magauer 2022-07-25 20:05:17 UTC
Created attachment 1899257 [details]
Screenshot from the npm install nodejs with the missing characters

And right after this I opened a Terminal window and typed:
- dnf install npm
- npm install nodejs

Comment 13 Lukas Magauer 2022-07-25 20:06:36 UTC
I'm very fine with reassigning wherever it needs to go to find a solution to that issue :)

Comment 14 Akira TAGOH 2022-07-26 04:06:07 UTC
Created attachment 1899333 [details]
another screenshot for woff2

BTW web browser replaces the system font with downloaded woff2 once they finished downloading. in other words, they may use the system font, particularly when it wasn't finished during initial rendering. you may want to check the network monitor on the web developer tools. I attach another screenshot for comparison. as you can see, there should be 6 requests related to fonts (one is a stylesheet and 5 for web fonts).

Comment 15 Jens Petersen 2022-07-26 11:32:16 UTC
(In reply to Lukas Magauer from comment #12)
> Created attachment 1899257 [details]
> Screenshot from the npm install nodejs with the missing characters
> 
> And right after this I opened a Terminal window and typed:
> - dnf install npm
> - npm install nodejs

You could try installing google-noto-sans-symbols2-fonts for the Braille characters.

Comment 16 Lukas Magauer 2022-07-27 19:23:53 UTC
Created attachment 1899782 [details]
Firefox with open dev tools network tab

> BTW web browser replaces the system font with downloaded woff2 once they finished downloading. in other words, they may use the system font, particularly when it wasn't finished during initial rendering. you may want to check the network monitor on the web developer tools. I attach another screenshot for comparison. as you can see, there should be 6 requests related to fonts (one is a stylesheet and 5 for web fonts).

Okay I think I see what you are talking about, there are 2 tries to download the u2c00.woff and .ttf files. Both fail with a CORS error. Maybe this is intentional, maybe not.
Which means maybe a website error?

But tbh this should only have been an easy way to make the npm character thing visible, if it is expected that there is no font fallback for Firefox, I'm fine with that, then it's really an npm package error, as this one really expects to have a font that supports these characters.

Comment 17 Lukas Magauer 2022-07-27 19:33:48 UTC
The same behavior definitely also happens on Fedora so yeah either website is broken or expected, that it should use the local provided fonts.

Comment 18 Lukas Magauer 2022-07-27 19:53:55 UTC
> You could try installing google-noto-sans-symbols2-fonts for the Braille characters.

So there was no symbols2 font available from the repos, only a symbols, but this one didn't fix it.
I can also see that this font is available in CentOS Stream 9's crb repo, but not in the RHEL 9 crb up to now.

So I grabbed the RPM from CentOS Stream now, but after installing, even rebooting, still the same behavior.

Comment 19 Lukas Magauer 2022-07-27 20:09:47 UTC
I further got told by the originating reporter, that this font fixed the issues for him: https://copr.fedorainfracloud.org/coprs/shassard/juliamono-fonts
So I tested this now as well and yes, after installing the copr package, it is possible to see the correct character in both the browser and also the terminal.

Comment 20 Lukas Magauer 2022-07-27 23:16:53 UTC
Also tried it on CentOS Stream 9 now, same behavior, installed symbols2 there then, and also still the same behavior.

Comment 21 Akira TAGOH 2022-07-28 11:25:17 UTC
Okay, reassigning to npm, to correct dependency for fonts. how about google-roboto-fonts? they should have glyphs for supplemental punctuation.

Comment 22 Lukas Magauer 2022-07-28 16:23:38 UTC
As far as I could find via dnf, there is only a google-roboto-slab-fonts package, which didn't fix the issue.
I then compared the installed fonts from my Fedora machine against the RHEL machine and... google-noto-sans-mono-fonts did the trick, after installing that the supplemental punctuations are showing up!

Comment 23 Lukas Magauer 2022-09-25 18:37:33 UTC
I think this issue has stalled somehow.
Any progress?

Comment 24 Jens Petersen 2022-09-26 04:02:01 UTC
I think for npm google-noto-sans-symbols2-fonts could be Recommended.

Comment 25 Jens Petersen 2022-09-26 04:04:09 UTC
(It would have been better also to have filed separate reports for the Supplemental Punctuation and the npm: this are not directly related.)

Comment 26 Jens Petersen 2022-09-26 04:08:06 UTC
(I think in Fedora the npm braille symbols render with Gdouros Symbola which we don't include in RHEL9,
but google-noto-sans-symbols2-fonts is available in CRB.)

Comment 27 Jens Petersen 2022-09-26 07:04:04 UTC
If I am not mistaken dejavu-sans-fonts also has Braille Pattern coverage.

Comment 28 Jens Petersen 2022-09-26 07:24:33 UTC
Lukas what is your output of `rpm -qa \*-fonts | sort`?

For me Braille renders fine in my RHEL9 in gnome-terminal.

Comment 29 Lukas Magauer 2022-09-26 17:11:11 UTC
Thank you for your time Jens!

> I think for npm google-noto-sans-symbols2-fonts could be Recommended.

As far as I can see, this package is not available for RHEL 9, couldn't find it neither with dnf nor with the online package browser. (also not in the codeready-builder repo)
I see it in CentOS Stream 9 though, there it is in the CRB repo.

> (It would have been better also to have filed separate reports for the Supplemental Punctuation and the npm: this are not directly related.)

Sorry I'm not very used to creating issues here, should I create a second one? :)


> Lukas what is your output of `rpm -qa \*-fonts | sort`?
> For me Braille renders fine in my RHEL9 in gnome-terminal.

Welp... I would guess it was already fixed in the meantime!
At least npm shows the parenthesis characters correctly now!
(Firefox still has the problem, but that's of course not a problem as we discovered if the websites provide there own fonts)
Great that it could be fixed somehow of course :)

Comment 30 Lukas Magauer 2022-09-26 17:16:10 UTC
Created attachment 1914408 [details]
List of installed packages with font in the name

Comment 31 Lukas Magauer 2022-09-26 17:17:05 UTC
Created attachment 1914409 [details]
Today's dnf update which fixed the problem for npm

Comment 33 RHEL Program Management 2023-09-20 15:05:42 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 34 RHEL Program Management 2023-09-20 15:07:52 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


Note You need to log in before you can comment on or make changes to this bug.