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 111471 - Gimp exits when no fonts found
Gimp exits when no fonts found
Status: RESOLVED DUPLICATE of bug 86150
Product: GIMP
Classification: Other
Component: General
1.x
Other All
: Normal normal
: 2.0
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2003-04-24 01:56 UTC by Cameron Gregory
Modified: 2003-11-02 15:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Cameron Gregory 2003-04-24 01:56:50 UTC
G'Day,
  I just built gimp (obviously not correctly), and it all runs
(and builds) just fine until I try to use the text tool, then when you
start to type text, you get:

No fonts found; this probably means that the fontconfig
library is not correctly configured. You may need to
edit the fonts.conf configuration file. More information
about fontconfig can be found in the fontconfig(3) manual
page and on http://fontconfig.org

pgimeno said he also experienced it, and suspects that it's actually
a pango bug.

I assume I still have something wrong with fontconfig, but still,
it shouldn't exit.

line 599 of pango/pangofc-fontmap.cI
is the culprit. (pango-1.2.1)

thanks,

Cameron
Comment 1 Raphaël Quinet 2003-04-24 09:11:06 UTC
A similar problem was reported for Script-Fu in bug #110227.  Another
case in which Pango causes the whole GIMP to exit was reported in
bug #107434 (marked as a duplicate of bug #101856, which was reassigned
to Pango).

I agree that it is definitely wrong to exit the whole GIMP if no fonts
can be found.  Although this problem is related to Pango, let's keep
this bug report open as a GIMP bug, focused on the fact that the whole
application should not exit even if the underlying toolkit cannot use
some (or any) fonts.
Comment 2 Sven Neumann 2003-04-24 09:46:57 UTC
That's not a bug. You need to have at least one font configured or
nothing will work. Please check your fontconfig setup. Does fc-list
list any fonts at all?
Comment 3 Sven Neumann 2003-04-24 09:47:52 UTC
BTW, it's not the application that exits here; Pango calls exit().
Comment 4 Cameron Gregory 2003-04-24 12:25:50 UTC
After I ran fc-cache -v (thanks to yosh).  It worked just fine.
But I imagine many people would use the gimp without using the
text tool (perhaps other tools would break too?)
Comment 5 Sven Neumann 2003-04-24 14:18:47 UTC
At least on X11 people are most probably using fontconfig for the
desktop font rendering anyway. So they need a reasonable font setup.
If Yosh finally commits the code related to bug #110798, we could have
a chance to workaround this and disable everything font-related in
case fontconfig is not setup correctly.
Comment 6 Cameron Gregory 2003-04-24 14:30:38 UTC
I was running it on my server and exporting to my laptop.  That could
explain why I didn't have the same problem on the laptop. thanks :-)
Comment 7 Alan Horkan 2003-07-23 18:40:36 UTC
Changes at the request of Dave Neary on the developer mailing list.  
I am changing many of the bugzilla reports that have not specified a target
milestone to Future milestone.  Hope that is acceptable.  
Comment 8 Dave Neary 2003-07-26 20:11:52 UTC
Changing milestone on a bunch of bugs to 2.0 - none of these could be considered
a blocker for a pre-release, IMHO. Many of these have patches or someone working
on them, but they're not urgent.

Dave.
Comment 9 Henrik Brix Andersen 2003-08-16 10:51:39 UTC
Yosh seems to already have committed code related to bug #110798 -
does that code fix this bug as well?
Comment 10 Sven Neumann 2003-09-04 12:18:47 UTC
Yosh, what does latest GIMP do when the user has no fonts configured?

I am tempted to resolve this bug as a duplicate of the "ship a font
with Pango to deal with impossibly broken configs" bug (#86150).
Comment 11 Sven Neumann 2003-11-02 15:25:31 UTC

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