Bug 804994 - GTK applications show empty boxes instead of characters and give PANGO errors
Summary: GTK applications show empty boxes instead of characters and give PANGO errors
Status: RESOLVED DUPLICATE of bug 806642
Alias: None
Product: openSUSE 12.2
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 12.2
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-21 15:04 UTC by Tilman Vogel
Modified: 2013-03-27 11:57 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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

Note You need to log in before you can comment on or make changes to this bug.
Description Tilman Vogel 2013-02-21 15:04:44 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0

During installation, somehow the /usr/lib*/pango/1.8.0/modules.cache does not get set up (even though there is a relating call in the postinstall scriptlet).

Running
pango-querymodules --update-cache
pango-querymodules-64 --update-cache

Fixed the problem for me.

The typical PANGO error message is:

(pavucontrol:26055): Pango-CRITICAL **: No modules found:
No builtin or dynamically loaded modules were found.
PangoFc will not work correctly.
This probably means there was an error in the creation of:
  '/etc/pango/pango.modules'
You should create this file by running:
  pango-querymodules > '/etc/pango/pango.modules'

(pavucontrol:26055): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin'

(pavucontrol:26055): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'


Reproducible: Didn't try
Comment 1 Dominique Leuenberger 2013-03-27 11:57:27 UTC 
Tracking it in bug #806642 (which was raised later, but has already much more debug in it by now).

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