After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 98672 - Make pango-fontset.cI print a warning when no fonts are present
Make pango-fontset.cI print a warning when no fonts are present
Status: RESOLVED FIXED
Product: pango
Classification: Platform
Component: general
unspecified
Other Linux
: Normal major
: 1.2.0
Assigned To: Owen Taylor
Owen Taylor
: 100509 100801 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-11-16 04:11 UTC by David Polberger
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Attachments
The file generated by "startx 2> X_ERR" (214.13 KB, text/plain)
2002-11-16 04:13 UTC, David Polberger
Details

Description David Polberger 2002-11-16 04:11:29 UTC
I just downloaded and compiled GARNOME 0.18.3. The compilation process went
fine, but GNOME fails to start. It's worth noting that GARNOME 0.13.0 is
also installed on this machine (as a different user), and it's working
fine. I believe that Pango is the culprit, due to what appears on standard
error when I "startx":

** (gnome-session:4190): CRITICAL **: file pango-fontset.c: line 84
(pango_fontset_get_font): assertion `fontset != NULL' failed

I'll attach the complete error log shortly.
Comment 1 David Polberger 2002-11-16 04:13:29 UTC
Created attachment 12334 [details]
The file generated by "startx 2> X_ERR"
Comment 2 David Polberger 2002-11-16 04:40:13 UTC
I've found the solution to the problem [1]. There wasn't a valid font
cache file. I simply ran fc-cache (as root), and GNOME started up
normally.

Shouldn't Pango at least generate a more informative error message? In
retrospect, it sounds reasonable that fontset == NULL, as it couldn't
find the cache. Why not simply generate the cache if it cannot be found?

Note, though, that I know next to nothing about fontconfig; thus, take
everything I say with a grain of salt. :-)

I'm leaving this bug open for now. Please close it if you feel that
the error messages being printed to the console are sufficient.

[1] http://mail.gnome.org/archives/garnome-list/2002-October/msg00280.html
Comment 3 Owen Taylor 2002-11-21 22:58:22 UTC
Note that the fc-cache problem is probably indicative
of a bug in your fontconfig; there is a fairly serious
bug in fontconfig-2.0 in this area.

But you probably could also reproduce this by other
misconfiguration.
Comment 4 Owen Taylor 2002-12-06 22:31:34 UTC
*** Bug 100509 has been marked as a duplicate of this bug. ***
Comment 5 Owen Taylor 2002-12-07 06:09:59 UTC
Sat Dec  7 01:05:25 2002  Owen Taylor  <otaylor@redhat.com>

        * pango/pangofc-fontmap.cI (pango_fc_font_map_get_patterns):
        Print out an informative error message and exit(1) if
        no fonts are found. (#98672)

With the error message being:

         g_printerr ("No fonts found; this probably means that the
fontconfig\n"
                      "library is not correctly configured. You may
need to\n"
                      "edit the fonts.conf configuration file. More
information\n"
                      "about fontconfig can be found in the
fontconfig(3) manual\n"
                      "page and on http://fontconfig.org\n");
Comment 6 Owen Taylor 2002-12-10 06:47:09 UTC
*** Bug 100801 has been marked as a duplicate of this bug. ***