GIMP crashes scrolling through fonts in Font tool

[VICKI HANSON]

Running win 2k Pro GIMP 2.01. Problem is that if I try to scroll through
fonts for the font tool in gimp it terminates the program. no error messages
it just closes. I have used earler versions of gimp on win 98 and Fedora
linux with no problems (at least none like this) anyone else see this or
have sugestions?

[Dennis Pitchforth]

Hi Vicki
I am experiencing the same problem in Windows XP Home. See my previous post
of the 27th. If you hear of a solution post he answer here and I will do
the same.

Regards Dennis

"VICKI HANSON" <javi...@verizon.net> wrote in message
news:dW3uc.7491$oh7....@nwrddc01.gnilink.net...

[loic]

In article <dW3uc.7491$oh7....@nwrddc01.gnilink.net>, javi1129
@verizon.net says...

sorry for my english but i'm french.

there is a problem with the gtk+ font.
uninstall gtk+ and reinstall it but without GTK Winp (without the font
option)

LOIC

[Michael Schumacher]

loic <adress...@aol.com> writes:

This won't help here. Installing without GTK-Wimp will help to avoid
some warnings that are caused by the font used by the GUI, but the
text tool crashes won't go away.

HTH,
Michael

--
The GIMP > http://www.gimp.org | IRC: irc://irc.gimp.org/gimp
Sodipodi > http://sodipodi.sf.net | IRC: irc://irc.gimp.org/sodipodi

[Ralph]

Gimp was bombing out for me until I deleted Wingding fonts.
It works fine now.
The name of the offending font will appear in the console window.

[Stefan M. Huber]

On Mon, 14 Jun 2004 01:42:31 GMT, Ralph <wob...@bobble.net> wrote:

> Gimp was bombing out for me until I deleted Wingding fonts.
> It works fine now.
> The name of the offending font will appear in the console window.

Hm, I am experiencing similar troubles. I removed some fonts from my
Windows font directory and put them into the GIMP font directory. I have
already worked with that setup. I don't know, if I restarted after moving
the fonts, though. (These were all fonts that I do not use except for
images)

I launched The GIMP today and whne it came to reading the fonts, GIMP
crashed with
(gimp-2.0.exe:380): GLib-CRITICAL **: file gconvert.c: line 498
(g_convert): ass
ertion `str != NULL' failed
which is the error message that Danny Korpan got in January and after
*adding* fonts.

I am using the latest stable release of The GIMP and downloaded
(uninstalled and installed) GTK+ that is offered for download on the same
page. --no-fonts is not an option for me, since I need the text tool for
the work I am about to do...

Any hints for me?

>> > sorry for my english but i'm french.

I'll never understand why people who write understandable English keep
excusing themselves for their English skills :)

Stefan,
Austrian
--
Das wars, was ich mit "barockem Programmieren" gemeint habe:
Schnoerkselmaximierung bis der Compiler mit einen ELACHKRAMPF aussteigt.
--- Alexander Talos in at.linux

[Stefan M. Huber]

On Wed, 07 Jul 2004 10:34:46 +0200, Stefan M. Huber <loos...@gmx.net>
wrote:

> On Mon, 14 Jun 2004 01:42:31 GMT, Ralph <wob...@bobble.net> wrote:
>
>> Gimp was bombing out for me until I deleted Wingding fonts.
>> It works fine now.
>> The name of the offending font will appear in the console window.
>
> Hm, I am experiencing similar troubles. I removed some fonts from my
> Windows font directory and put them into the GIMP font directory. I have
> already worked with that setup. I don't know, if I restarted after
> moving the fonts, though. (These were all fonts that I do not use except
> for images)
>
> I launched The GIMP today and whne it came to reading the fonts, GIMP
> crashed with
> (gimp-2.0.exe:380): GLib-CRITICAL **: file gconvert.c: line 498
> (g_convert): ass
> ertion `str != NULL' failed
> which is the error message that Danny Korpan got in January and after
> *adding* fonts.

<http://gug.sunsite.dk/forum/?threadid=1573>, halfway through the page
posted by Kevin and Xenzat.

I wonder, where that comes from, though.

Stefan

[Stefan M. Huber]

It is driving me mad!

On Wed, 07 Jul 2004 10:49:28 +0200, Stefan M. Huber <loos...@gmx.net>
wrote:

>> I launched The GIMP today and whne it came to reading the fonts, GIMP

>> crashed with
>> (gimp-2.0.exe:380): GLib-CRITICAL **: file gconvert.c: line 498
>> (g_convert): ass
>> ertion `str != NULL' failed
>> which is the error message that Danny Korpan got in January and after
>> *adding* fonts.
>
> <http://gug.sunsite.dk/forum/?threadid=1573>, halfway through the page
> posted by Kevin and Xenzat.

The GIMP crashes again when accessing font folders. But different to last
time (I haven't used The GIMP since I last fixed the problem), There are
onle these entries in .fonts.-cache-1:
/usr/X11R6/lib/X11/fonts/Type1" 0 1043794360 ".dir"
"/usr/X11R6/lib/X11/fonts" 0 1063704586 ".dir"
"/usr/X11R6/lib/X11/fonts/encodings" 0 1077748597 ".dir"
"/usr/X11R6/lib/X11/fonts/75dpi" 0 1077748621 ".dir"
"/usr/X11R6/lib/X11/fonts/misc" 0 1077748624 ".dir"
"/usr/X11R6/lib/X11/fonts/util" 0 1077748597 ".dir"

The thing is: This file used to be longer. Much longer. And there were
Windows paths in it (I am on Win2k). My HOME variable points to H: which
is a mounted Linux share. I do not have The GIMP on Linx,; can any other
application (I use Linux mostly as server OS) overwrite this file and do
harm to my Windows GIMP? If so, why has that only started with GIMP 2?

After removing the font cache file, The GIMP recreated it again with the
invalid characters near ProFont entries. Removing them cured the problem.
Once again.

Stefan
--
BUGS: None. Mutts have fleas, not bugs.
--- taken from the mutt manpage

[jlon...@gmail.com]

And back from the dead, yeah you guessed it... this thread! I know this is an old thread just though it was interesting to see such an old problem that still exists. I'm running win 7 and gimp 2.8.6 and this problem just kills me.