RSS/Atom feed Twitter
Site is read-only, email is disabled

Problem starting gimp-1.3.23

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

7 of 8 messages available
Toggle history

Please log in to manage your subscriptions.

Problem starting gimp-1.3.23 Frank Wittemeier 18 Dec 16:20
  Problem starting gimp-1.3.23 Sven Neumann 18 Dec 17:45
   Problem starting gimp-1.3.23 Frank Wittemeier 04 Jan 18:42
    Problem starting gimp-1.3.23 Sven Neumann 04 Jan 21:54
3FE1D8EB.9030301@free.fr 07 Oct 20:22
  Problem starting gimp-1.3.23 Frank Wittemeier 21 Dec 12:26
   Problem starting gimp-1.3.23 Sven Neumann 21 Dec 13:57
    Problem starting gimp-1.3.23 David Neary 21 Dec 15:24
Frank Wittemeier
2003-12-18 16:20:24 UTC (almost 21 years ago)

Problem starting gimp-1.3.23

Hi,

I have a problem starting gimp 1.3.23. I compiled it with no problems after installing all the necessary libraries. When I start gmip I get the follwing error:

frawi@frawibook:~> gimp-1.3 This is a development version of The GIMP. Debug messages may appear here.

gimp_composite: use=yes, verbose=no +mmx -sse -sse2 -3dnow -altivec -vis

(gimp-1.3:1395): GLib-GObject-WARNING **: specified class size for type `PangoXftFontMap' is smaller than the parent type's `PangoFontMap' class size

(gimp-1.3:1395): GLib-GObject-CRITICAL **: file gobject.c: line 615 (g_object_new): assertion `G_TYPE_IS_OBJECT (object_type)' failed gimp-1.3: fatal error: Speicherzugriffsfehler gimp-1.3 (pid:1395): [E]xit, [H]alt, show [S]tack trace or [P]roceed:

gimp 1.3.7 worked well before. I compiled the libs and gimp several times but no help.

Can someone help me please?

Thanks Frank

Sven Neumann
2003-12-18 17:45:16 UTC (almost 21 years ago)

Problem starting gimp-1.3.23

Hi,

Frank Wittemeier writes:

(gimp-1.3:1395): GLib-GObject-WARNING **: specified class size for type `PangoXftFontMap' is smaller than the parent type's `PangoFontMap' class size

This indicates that something is severely broken with your Pango libraries. 'make clean' in Pango and rebuilding it should fix the problem.

Sven

Frank Wittemeier
2003-12-21 12:26:12 UTC (almost 21 years ago)

Problem starting gimp-1.3.23

Hi,

sorry Dave and Sven, I made a mistake replying to your mails.

Am Donnerstag, 18. Dezember 2003 17:42 schrieb Dave Neary:

Hi Frank,

Frank Wittemeier wrote:

frawi@frawibook:~> gimp-1.3
(gimp-1.3:1395): GLib-GObject-WARNING **: specified class size for type `PangoXftFontMap' is smaller than the parent type's `PangoFontMap' class size

It appears you've run into a frequently found bug - you do not have any fonts installed where freefont can find them. Since around 1.3.15, we

I have installed TrueType fonts in /usr/X11R6/lib/X11/fonts/truetype/, other applications use this fonts (OpenOffice).

have been using freefont for fonts. If you do not have any true-type fonts installed, then the GIMP will not start by default.

Is freefont included in gimp or is it an extra package? I have installed the packeges an libraries listed on wiki.gimp.org/gimp/GimpFromSource.

To test this theory, try running gimp-1.3 --no-fonts

The same error :-(

gimp 1.3.7 worked well before. I compiled the libs and gimp several times but no help.

You might consider running make uninstall in the gimp 1.3.7 source directory, then re-running make install in the newer sources. Several files have been removed in the meantime which might cause you problems.

Yes, I did this before.

Hope that helps,
Dave.

Not yet, any other hints?
Frank

Sven Neumann
2003-12-21 13:57:18 UTC (almost 21 years ago)

Problem starting gimp-1.3.23

Hi,

Frank Wittemeier writes:

(gimp-1.3:1395): GLib-GObject-WARNING **: specified class size for type `PangoXftFontMap' is smaller than the parent type's `PangoFontMap' class size

It appears you've run into a frequently found bug - you do not have any fonts installed where freefont can find them. Since around 1.3.15, we

Sorry, but what Dave wrote here is wrong and will only confuse Frank (especially since Dave wrote freefont when he probably meant to write fontconfig). Look at the error message. The problem isn't missing fonts but a miscompiled Pango library. Either Frank is linking libpangoxft with a wrong version of libpango or he compiled the pango libraries against a wrong set of Pango headers.

Sven

David Neary
2003-12-21 15:24:48 UTC (almost 21 years ago)

Problem starting gimp-1.3.23

Hi,

Sven Neumann wrote:

Sorry, but what Dave wrote here is wrong and will only confuse Frank (especially since Dave wrote freefont when he probably meant to write fontconfig). Look at the error message. The problem isn't missing fonts but a miscompiled Pango library. Either Frank is linking libpangoxft with a wrong version of libpango or he compiled the pango libraries against a wrong set of Pango headers.

Yes, I had a brainfart. I mean fontconfig which, as both Frank and Sven have pointed out, was not the problem.

Cheers, Dave.

Frank Wittemeier
2004-01-04 18:42:55 UTC (almost 21 years ago)

Problem starting gimp-1.3.23

Hi,

Am Donnerstag, 18. Dezember 2003 17:45 schrieb Sven Neumann:

Hi,

Frank Wittemeier writes:

(gimp-1.3:1395): GLib-GObject-WARNING **: specified class size for type `PangoXftFontMap' is smaller than the parent type's `PangoFontMap' class size

This indicates that something is severely broken with your Pango libraries. 'make clean' in Pango and rebuilding it should fix the problem.

after uninstalling and installing some libraries (glib, pango, atk and gtk+) and recompiling gimp-1.3.23 there is only one error left:

frawi@frawibook:~/src/gimp-1.3.23> gimp-1.3 This is a development version of The GIMP. Debug messages may appear here.

gimp_composite: use=yes, verbose=no +mmx -sse -sse2 -3dnow -altivec -vis gimp-1.3: fatal error: Speicherzugriffsfehler gimp-1.3 (pid:1612): [E]xit, [H]alt, show [S]tack trace or [P]roceed: s #0 0x404b75d4 in g_on_error_stack_trace (prg_name=0x830fbd0 "gimp-1.3") #1 0x404b74ee in g_on_error_query (prg_name=0x830fbd0 "gimp-1.3") #2 0x08081c1a in gimp_eek (reason=0x8208296 "fatal error", #3 0x08081b76 in gimp_fatal_error () at errors.c:118 #4 0x080816e5 in gimp_sigfatal_handler () at main.c:571 #5
#6 0x4064593f in free () from /lib/libc.so.6 #7 0x4057b27f in ft_free (memory=0x83762a0, block=0x1) #8 0x4057b68e in FT_Free (memory=0x83762a0, P=0x8375c08) #9 0x405b29ec in T1_Face_Done (face=0x8375a60) #10 0x4057eaed in destroy_face (memory=0x83762a0, face=0x8375a60, #11 0x4057fd5a in FT_Done_Face (face=0x8375a60) #12 0x405352ef in FcFreeTypeQuery (
#13 0x40535b57 in FcFileScan (set=0x835c6a0, dirs=0x8358d60, cache=0x835a778, #14 0x40535e74 in FcDirScan (set=0x835c6a0, dirs=0x8358d60, cache=0x835a778, #15 0x40538d2d in FcConfigBuildFonts (config=0x8358cf8) at fccfg.c:206 #16 0x40533b88 in FcInitLoadConfigAndFonts () at fcinit.c:83 #17 0x40533bd3 in FcInit () at fcinit.c:101

Any hints whats wrong now?

Sven

Thanks
Frank

Sven Neumann
2004-01-04 21:54:22 UTC (almost 21 years ago)

Problem starting gimp-1.3.23

Hi,

Frank Wittemeier writes:

after uninstalling and installing some libraries (glib, pango, atk and gtk+) and recompiling gimp-1.3.23 there is only one error left:

frawi@frawibook:~/src/gimp-1.3.23> gimp-1.3 This is a development version of The GIMP. Debug messages may appear here.

gimp_composite: use=yes, verbose=no +mmx -sse -sse2 -3dnow -altivec -vis gimp-1.3: fatal error: Speicherzugriffsfehler gimp-1.3 (pid:1612): [E]xit, [H]alt, show [S]tack trace or [P]roceed: s #0 0x404b75d4 in g_on_error_stack_trace (prg_name=0x830fbd0 "gimp-1.3") #1 0x404b74ee in g_on_error_query (prg_name=0x830fbd0 "gimp-1.3") #2 0x08081c1a in gimp_eek (reason=0x8208296 "fatal error", #3 0x08081b76 in gimp_fatal_error () at errors.c:118 #4 0x080816e5 in gimp_sigfatal_handler () at main.c:571 #5
#6 0x4064593f in free () from /lib/libc.so.6 #7 0x4057b27f in ft_free (memory=0x83762a0, block=0x1) #8 0x4057b68e in FT_Free (memory=0x83762a0, P=0x8375c08) #9 0x405b29ec in T1_Face_Done (face=0x8375a60) #10 0x4057eaed in destroy_face (memory=0x83762a0, face=0x8375a60, #11 0x4057fd5a in FT_Done_Face (face=0x8375a60) #12 0x405352ef in FcFreeTypeQuery (
#13 0x40535b57 in FcFileScan (set=0x835c6a0, dirs=0x8358d60, cache=0x835a778, #14 0x40535e74 in FcDirScan (set=0x835c6a0, dirs=0x8358d60, cache=0x835a778, #15 0x40538d2d in FcConfigBuildFonts (config=0x8358cf8) at fccfg.c:206 #16 0x40533b88 in FcInitLoadConfigAndFonts () at fcinit.c:83 #17 0x40533bd3 in FcInit () at fcinit.c:101

Any hints whats wrong now?

Judging from the stack trace, this looks like a known bug in the freetype T1 parser (version 2.1.5 if I remember correctly). You should update to a newer version of freetype2.

Sven