Bug 1860412

Summary: New version of Droid Sans causes problems in Firefox and Thunderbird GUIs
Product: [Fedora] Fedora Reporter: Stanislav Kontar <skontar>
Component: google-droid-fontsAssignee: Nicolas Mailhot <nicolas.mailhot>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: fonts-bugs, nicolas.mailhot, oliver, paul, tremble
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 16:35:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshots none

Description Stanislav Kontar 2020-07-24 13:41:33 UTC 
Description of problem:
For years I am using Droid Sans 11 as my GUI font in my desktop. With recent update the text in Firefox and Thunderbird gained weird padding, causing wasted space, weird alignment issues, sometimes slight text cut-off at bottom (Thunderbird).

Version-Release number of selected component (if applicable):
google-droid-sans-fonts-20200215-3.fc32.noarch
Last good: google-droid-sans-fonts-20120715-16.fc31.noarch

How reproducible:
Set Droid Sans 11 (also different size) as a GUI font. See how menus and parts of GUI looks like, overlaps and behaves. Compare by testing old version of the package, or different font such as Roboto.

Steps to Reproduce:
1. Install google-droid-sans-fonts-20200215-3.fc32.noarch
2. Set Droid Sans 11 as default a GUI font
3. Open Thunderbird or Firefox

Actual results:
Weird unnecesarry padding in menus, cut-offs and similar text issues.

Expected results:
No change when compared to old version.

Additional info:
Reproducible in clean XFCE spin VM. Easily fixed by using similar font (Roboto) or old version of the package, so the problem is in the font package.
Comment 1 Stanislav Kontar 2020-07-24 13:46:16 UTC 
Created attachment 1702348 [details]
Screenshots

Files with "a" suffix - before update. Files with "b" suffix - after update.
Especially notice letters like "g" cut off in t2b.png file.
Comment 2 Fedora Program Management 2021-04-29 16:34:20 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 3 Ben Cotton 2021-05-25 16:35:19 UTC 
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.