Bug 15006 - [m5b2] default xfce installation - terminal does not use monospace font
Summary: [m5b2] default xfce installation - terminal does not use monospace 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: Jani Välimaa
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-11 02:04 CET by Florian Hubold
Modified: 2015-06-03 22:43 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
screenshot of terminal showing installed font packages (327.77 KB, image/png)
2015-01-11 02:04 CET, Florian Hubold 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Florian Hubold 2015-01-11 02:04:08 CET 
Created attachment 5801 [details]
screenshot of terminal showing installed font packages

After installing XFCE from beta2 dual dvd, the terminal does not use a monospace font. Under preferences -> appearance -> font only 5 fonts are selectable, and they all look the same (dejavu sans ?). Monospace is selected by default, but no monospace font is used.

fonts-ttf-dejavu and fonts-dejavu-common are installed.

Also the main appearance dialog for xfce does only offer those 5 fonts and behaves similar.


When running xfce4-terminal in a different desktop session, e.g. under lxqt, the cantarell monospace font is used and it looks normal.
Florian Hubold 2015-01-11 02:06:14 CET

CC: (none) => doktor5000
Assignee: bugsquad => jani.valimaa

Comment 1 Jani Välimaa 2015-01-11 06:47:40 CET 
See what happens if you run 'fc-cache -s' as root or install some fonts which launches the filetrigger.
Comment 2 Florian Hubold 2015-01-11 19:19:28 CET 
fc-cache -s alone changes nothing. After installing bitmap-fixed-fonts the appearance dialog shows it as monospace font, and selecting it shows it in terminal. The other fonts still look all the same.
claire robinson 2015-01-12 10:54:29 CET

CC: (none) => eeeemail

Comment 3 Jani Välimaa 2015-03-07 19:33:38 CET 
Is this still valid?
Comment 4 Shlomi Fish 2015-06-03 18:17:13 CEST 
(In reply to Jani Välimaa from comment #3)
> Is this still valid?

I'm going to test this bug in a VM. Stay tuned.

CC: (none) => shlomif

Comment 5 Shlomi Fish 2015-06-03 18:48:53 CEST 
(In reply to Shlomi Fish from comment #4)
> (In reply to Jani Välimaa from comment #3)
> > Is this still valid?
> 
> I'm going to test this bug in a VM. Stay tuned.

Seems fine in an x86-64 VirtualBox VM. Closing as fixed.

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

Comment 6 Florian Hubold 2015-06-03 22:43:12 CEST 
Thanks for re-testing, didn't get around to it yet :)
Note You need to log in before you can comment on or make changes to this bug.