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 1656262 - The terminal's character display is unclear on rhel8 guest after installing gnome
Summary: The terminal's character display is unclear on rhel8 guest after installing g...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gsettings-desktop-schemas
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: Carlos Garnacho
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-05 04:52 UTC by liuzi
Modified: 2020-11-04 01:35 UTC (History)
11 users (show)

Fixed In Version: 3.32.0-5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:34:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot of guest-terminal (1.07 MB, image/png)
2018-12-05 04:52 UTC, liuzi 		no flags Details
the font related packages on guest (979 bytes, text/plain)
2018-12-05 04:54 UTC, liuzi 		no flags Details
the font related packages on physical machine (1.62 KB, text/plain)
2018-12-05 04:58 UTC, liuzi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4451 0 None None None 2020-11-04 01:34:32 UTC

Description liuzi 2018-12-05 04:52:17 UTC 
Created attachment 1511530 [details]
screenshot of guest-terminal

Description of problem:
The terminal's character display is unclear on rhel8 guest after installing gnome

Version-Release number of selected component (if applicable):
host:kernel-4.18.0-40.el8.x86_64
guest:gnome-terminal-3.28.2-3.el8.x86_64
      vte291-0.52.2-2.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Install rhel8 guest in virt-manager on rhel8 server
2.Configure baseOS and Appstream repo in guest and install GUI for rhel8 guest

#yum install gnome*
# yum install xorg-x11*
# systemctl set-default graphical.target

3.Reboot the guest after installing all related GUI packages and open the terminal.
 
Actual results:
The terminal's character display is unclear on rhel8 guest after installing gnome

Expected results:
The terminal's character display should be clear on rhel8 guest after installing gnome


Additional info:
1.Can reproduce on rhel8 guest which on VMware
2.Can display normally on physical machine 
3.In comparison of the packages installed on physical machines (which display clearly and nicely), some packages are missing on the installation in guest os.please refer to attachments.
Comment 1 liuzi 2018-12-05 04:54:57 UTC 
Created attachment 1511531 [details]
the font related packages  on guest
Comment 2 liuzi 2018-12-05 04:58:39 UTC 
Created attachment 1511532 [details]
the font related packages on physical machine
Comment 3 Christian Persch 2018-12-10 18:08:02 UTC 
This is using a proportional font instead of a monospace one; that's not supported.
Comment 4 liuzi 2018-12-11 08:24:21 UTC 
1.After the guest's GUI installation is completed，no default settings for the terminal font have been modified.
2.After modifying the guest's font, the terminal's character display is normal.
Comment 5 Jens Petersen 2020-02-07 15:39:08 UTC 
You simply don't have enough fonts installed

Please run the command:

 sudo yum install @fonts


I don't know how you installed the VM but it is much easier if you install a desktop configuration: ie Workstation or Server etc.


I dunno if a weak dependency on dejavu-sans-mono-fonts could be added to gnome-terminal to alleviate this?
Comment 6 Debarshi Ray 2020-02-07 16:00:29 UTC 
This is similar to https://bugzilla.redhat.com/show_bug.cgi?id=1677056 but I think the details are a bit different. It's very likely a gsettings-desktop-schemas problem.
Comment 7 Debarshi Ray 2020-02-07 16:12:36 UTC 
In gsettings-desktop-schemas 3.31.90 (eventually GNOME 3.32 and Fedora 30), the default monospace font was changed to "Source Code Pro 10" from the previous "Monospace 11". See:
https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/merge_requests/17

Then the Fedora package was updated to Recommend font(sourcecodepro). See:
https://src.fedoraproject.org/rpms/gsettings-desktop-schemas/c/5078dfad955967456e7fb56e1b18ccc4d7c2d5b8
https://bugzilla.redhat.com/show_bug.cgi?id=1677056

These changes are in the rhel-8.2.0 branch of gsettings-desktop-schemas. However, it also overrides the default monospace font back to "Monospace 11". See:
https://bugzilla.redhat.com/show_bug.cgi?id=1715761

Now there's no adobe-source-code-pro-fonts package in RHEL. It seems to be that the Recommends in the gsettings-desktop-schemas RPM (ie., "font(sourcecodepro) from adobe-source-code-pro-fonts") don't match the default in the schema itself (ie., overridden to "Monospace 11").
Comment 8 Jens Petersen 2020-02-10 05:18:10 UTC 
(In reply to Debarshi Ray from comment #7)
> In gsettings-desktop-schemas 3.31.90 (eventually GNOME 3.32 and Fedora 30),
> the default monospace font was changed to "Source Code Pro 10" from the
> previous "Monospace 11". See:
> https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/merge_requests/17
> 
> Then the Fedora package was updated to Recommend font(sourcecodepro). See:
> https://src.fedoraproject.org/rpms/gsettings-desktop-schemas/c/
> 5078dfad955967456e7fb56e1b18ccc4d7c2d5b8
> https://bugzilla.redhat.com/show_bug.cgi?id=1677056
> 
> These changes are in the rhel-8.2.0 branch of gsettings-desktop-schemas.
> However, it also overrides the default monospace font back to "Monospace
> 11". See:
> https://bugzilla.redhat.com/show_bug.cgi?id=1715761
> 
> Now there's no adobe-source-code-pro-fonts package in RHEL. It seems to be
> that the Recommends in the gsettings-desktop-schemas RPM (ie.,
> "font(sourcecodepro) from adobe-source-code-pro-fonts") don't match the
> default in the schema itself (ie., overridden to "Monospace 11").

I think it would be good to file a separate bug for this.
Comment 9 Akira TAGOH 2020-02-10 05:27:34 UTC 
(In reply to Debarshi Ray from comment #7)
> Now there's no adobe-source-code-pro-fonts package in RHEL. It seems to be
> that the Recommends in the gsettings-desktop-schemas RPM (ie.,
> "font(sourcecodepro) from adobe-source-code-pro-fonts") don't match the
> default in the schema itself (ie., overridden to "Monospace 11").

This is the reason. fontconfig doesn't know where "fonts" is classified in generic family names. if no such fonts are installed, fontconfig tries to fall back to sans-serif anyway. that is the side effect of having certain font name there.
Comment 10 Debarshi Ray 2020-02-10 11:45:08 UTC 
Reassigning to gsettings-desktop-schemas to get the Recommends in the RPM to match the actual (overridden) settings.
Comment 11 Debarshi Ray 2020-02-10 12:37:26 UTC 
@Akira, @Jens, or anybody more knowledgeable than me,

What's the default monospace font that we expect a RHEL GNOME session to have? I guess it's the same defaults that Fedora and upstream GNOME used to have before the default changed in Fedora 30?

Is it DejaVu Sans Mono from the dejavu-sans-mono-fonts RPM? If so, then 'Recommends: font(dejavusansmono)' should be correct, right?
Comment 13 Akira TAGOH 2020-02-10 12:49:07 UTC 
Yes, DejaVu Sans Mono is default monospace font.
Comment 21 Michal Odehnal 2020-07-24 08:55:45 UTC 
Unable to reproduce with gsettings-desktop-schemas-3.32.0-5.el8.x86_64
Comment 24 errata-xmlrpc 2020-11-04 01:34:13 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: GNOME security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4451
Note You need to log in before you can comment on or make changes to this bug.