Description of Problem: Gnumeric fails to start complaining about font problems and suggesting I check gnome-print. How Reproducible: Always. Steps to Reproduce: 1. Default install. 2. Picked en_GB locale (dunno whether relevant), and started Gnome via gdm 3. Started gnumeric from foot menu (same thing happens when starting from command line after ssh'ing in). Actual Results: Dialogue box: "Gnumeric failed to find a suitable default font. Please verify your gnome-print installation. Your fontmap file could not be found in the expected location." It then suggested the wrong url for bugs (it's bugzilla.gnome.org not bugs.gnome.org now) and a set of information to include with the report. Expected Results: I expected it to run :) Additional Information: The dialogue box says it's expecting /usr/share/fonts/fontmap [hobbit@pwca hobbit]$ locate fontmap /usr/share/fonts/fontmap2 /usr/share/texmf/xdvi/vfontmap /usr/include/kpathsea/fontmap.h /usr/include/pango-1.0/pango/pango-fontmap.h LC_ALL is unset. LANG -- well, when starting gnome from gdm it's en_GB.ISO-8859-1 and when trying it again by ssh'ing in it was en_US. And the libxml version is 1.8.11-3 When starting from a terminal, I get this in the terminal: ** CRITICAL **: file gnome-font-face.c: line 306 (gnome_font_unsized_closest): assertion `face != NULL' failed. ** CRITICAL **: file gnome-font.c: line 244 (gnome_font_new_closest): assertion `face != NULL' failed. ** CRITICAL **: file gnome-rfont.c: line 963 (create_display_font): assertion `gnomefont != NULL' failed.
This defect considered MUST-FIX for Fairfax gold-release.
While I don't know the exact problem that was happening here to cause an empty /usr/share/font/fontmap2, I changed the handling of the fontmap a lot in the new gnome-print-0.29-2 RPM and hopefully this will no longer occur. (The fontmap is now in /etc/gnome/fonts/fontmap2, among other things.) The new RPM fixes a system that was broken in this way when upgrading to it, so that's a decent indication that it is now fixed.
*** Bug 46901 has been marked as a duplicate of this bug. ***