Bug 24524 - The default monospace font for GNOME is not available, and the fallback font is illegible
Summary: The default monospace font for GNOME is not available, and the fallback font ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-17 17:00 CET by Martin Whitaker
Modified: 2019-03-18 21:30 CET (History)
2 users (show)

See Also:
Source RPM: gsettings-desktop-schemas-3.32.0-1
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Martin Whitaker 2019-03-17 17:00:01 CET 
In the update to GNOME 3.32, the default monospace font for the GNOME desktop has been changed from "Monospace" to "Source Code Pro". The new font does not appear to be available in Mageia. The font that fontconfig falls back to is almost illegible.

Either the Source Code Pro font needs to be imported into Mageia and added as a dependency, or the default needs to be changed.
Comment 1 Marja Van Waes 2019-03-17 17:39:41 CET 
(In reply to Martin Whitaker from comment #0)
> In the update to GNOME 3.32, the default monospace font for the GNOME
> desktop has been changed from "Monospace" to "Source Code Pro". The new font
> does not appear to be available in Mageia. The font that fontconfig falls
> back to is almost illegible.
> 
> Either the Source Code Pro font needs to be imported into Mageia and added
> as a dependency, or the default needs to be changed.

Assigning to the Gnome maintainers.

Assignee: bugsquad => gnome
CC: (none) => marja11

Comment 2 David GEIGER 2019-03-18 07:00:11 CET 
Should be fixed importing fonts-otf-adobe-source-code-pro in Cauldron and adding it as a recommended package in gsettings-desktop-schemas.

CC: (none) => geiger.david68210

Comment 3 Martin Whitaker 2019-03-18 21:30:03 CET 
Confirmed. Thanks David.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.