Bug 16318 - Gnome Terminal unable to use Fixed SemiCondensed Font
Summary: Gnome Terminal unable to use Fixed SemiCondensed Font
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-07-07 11:16 CEST by Herbert Poetzl
Modified: 2016-10-09 12:27 CEST (History)
2 users (show)

See Also:
Source RPM: gnome-terminal-3.14.2-1.mga5
CVE:
Status comment:


Attachments

Description Herbert Poetzl 2015-07-07 11:16:07 CEST
Description of problem:
The Gnome Terminal Profile Preferences allow to select the Fixed SemiCondensed Font but instead always uses Liberation Mono Regular. Note that Fixed SemiCondensed is installed and enabled, and shows correctly in gnome-font-viewer as well as xfontsel.

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

How reproducible:
Always

Steps to Reproduce:
1. Make sure Fixed SemiCondensed is installed and enabled.
2. Select Edit->Profile Preferences 
3. Check Custom Font and select Fixed SemiCondensed
4. Watch Gnome Terminal to ignore the selection and present Liberation Mono Regular.


Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2016-10-09 10:50:33 CEST
Is this bug still valid?

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

Comment 2 Herbert Poetzl 2016-10-09 11:56:00 CEST
No idea. 

The bug was filed more than a year ago and I switched to xfce4-terminal which has all the features I need and the gnome terminal is missing.

Best,
Herbert

CC: (none) => herbert

Comment 3 Marja Van Waes 2016-10-09 12:27:20 CEST
(In reply to Herbert Poetzl from comment #2)
> No idea. 
> 
> The bug was filed more than a year ago and I switched to xfce4-terminal
> which has all the features I need and the gnome terminal is missing.
> 
> Best,
> Herbert

Closing as OLD, then, because no one else reported this issue

@ anyone who still hits this issue: please reopen this report

Status: NEW => RESOLVED
Resolution: (none) => OLD


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