Bug 1626909 - [freetype] bold font weight applied in gnome-terminal depending on the font size
Summary: [freetype] bold font weight applied in gnome-terminal depending on the font size
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: freetype
Version: 29
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-10 05:35 UTC by Joachim Frieben
Modified: 2019-11-27 22:09 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 22:09:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joachim Frieben 2018-09-10 05:35:16 UTC
Description of problem:
For current Fedora 29, the bold variant of font "Clean Regular" included in package xorg-x11-fonts-misc is applied or not in gnome-terminal depending on the font size. As a consequence, e.g., the output of the 'top' command is rendered with normal font weight alone at font size 15 but correctly mixed with normal and bold font weight at font size 16.

Version-Release number of selected component (if applicable):
gtk3-3.24.0-3.fc29

How reproducible:
Always

Steps to Reproduce:
1. Include collection of miscellaneous X11 fonts in the font path of gnome-terminal.
2. Choose font "Clean Regular" with size 15 in gnome-terminal.
3. Run 'top'.

Actual results:
Output is printed with characters of normal weight alone.

Expected results:
Output is printed with mixed characters of normal and bold weight just like when the terminal font is the default font.

Additional info:
- After setting the font size to 16, the output of 'top' looks as expected.
- The issue is absent from current Fedora 28.
- The issue persists after downgrading fontconfig to fontconfig-2.13.0-8.fc29 which is equivalent to fontconfig-2.13.0-4.fc28 included in Fedora 28.
- Fedora 29 includes gnome-terminal-3.28.2-4.fc29 which appears to be equivalent to gnome-terminal-3.28.2-2.fc28 included in Fedora 28.

Comment 1 Joachim Frieben 2018-11-21 19:30:59 UTC
Issue persists for gtk3-3.24.1-1.fc29.

Comment 2 Joachim Frieben 2019-04-28 16:37:40 UTC
Running 'pango-view --font="Clean Bold" --backend=ft2 -t "PANGO font rendering"' shows a font of normal weight whereas backends "cairo" and "xft" lead to the sample text being rendered with the bold font. This behaviour points to a problem with the freetype package.

Comment 3 Ben Cotton 2019-10-31 19:32:39 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-11-27 22:09:49 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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