Bug 354010 - Font preview not displaying properly
Summary: Font preview not displaying properly
Status: RESOLVED DUPLICATE of bug 336089
Alias: None
Product: kfontview
Classification: Applications
Component: general (show other bugs)
Version: 5.2.2
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-17 18:17 UTC by William
Modified: 2015-10-19 22:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Font Preview showing no font previews (49.61 KB, image/png)
2015-10-17 18:17 UTC, William 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description William 2015-10-17 18:17:34 UTC 
Created attachment 95021 [details]
Font Preview showing no font previews

When opening the Font Viewer from the command line, the results are that the previewed font is not displaying properly. The preview window is mostly blank with small artifacts appearing on the left and right edges of the preview window.

I have tried selecting various preview modes besides 'Standard Preview' and observed the same results.
I have tried zooming in and zooming out and observed the same results.
I have tried with several other system fonts and user fonts and observed the same results.

Steps to replicate:
1. Open a terminal window
2. Run the command: kfontview
3. Open a system font, e.g., /usr/share/fonts/truetype/oxygen-fonts/Oxygen-Sans.ttf

Expected results: The opened font should display in the preview area.
Actual results: The opened font is not displayed in the preview area.

System information:
Version: 5.2.2
OS: Linux (x86_64) release 3.19.0-30-generic
Renderer: GeForce GTX 660 Ti/PCIe/SSE2
OpenGL version: 4.5.0 NVIDIA 346.96
Look And Feel: Breeze
Desktop theme: Oxygen

Other observations:
Utilizing other font preview software such as Fonty Python or Speciman Font Previewer the font previews were displayed correctly.
Comment 1 Christoph Feck 2015-10-19 22:23:24 UTC 

*** This bug has been marked as a duplicate of bug 336089 ***