Bug 1678683 - The default font in Gnome Terminal looks bad.
Summary: The default font in Gnome Terminal looks bad.
Keywords:
Status: CLOSED DUPLICATE of bug 1677056
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-19 11:35 UTC by Lukas Ruzicka
Modified: 2019-02-24 00:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-24 00:03:05 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Ugly terminal font (107.06 KB, image/png)
2019-02-19 11:35 UTC, Lukas Ruzicka 		no flags Details
Tweaks settings (51.52 KB, image/png)
2019-02-19 11:36 UTC, Lukas Ruzicka 		no flags Details
View All

Description Lukas Ruzicka 2019-02-19 11:35:48 UTC 
Created attachment 1536292 [details]
Ugly terminal font

Description of problem:

After a pure installation of Fedora Rawhide (compose 20190217), the terminal font looks totally ugly (see screenshot).

Installing Gnome Tweaks revelead, that there was no default monospace font set. The problem disappeared when monospace font was set through Gnome Tweaks. 

Alternatively, choosing a custom font in Terminal preferences helped, too.

Version-Release number of selected component (if applicable):

gnome-shell-3.31.90-2.fc30.x86_64
gnome-terminal-3.30.2-2.fc30.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Install a fresh Fedora Rawhide and run the terminal after GIS has finished.

Actual results:

No default monospace font is set.

Expected results:

Default monospace font is set, so that terminal does not fall back to some ugly replacement.
Additional info:
Comment 1 Lukas Ruzicka 2019-02-19 11:36:25 UTC 
Created attachment 1536293 [details]
Tweaks settings
Comment 2 Chris Murphy 2019-02-24 00:03:05 UTC 

*** This bug has been marked as a duplicate of bug 1677056 ***
Note You need to log in before you can comment on or make changes to this bug.