Opened 15 years ago

Closed 14 years ago

#7950 closed defect (fixed)

Problem with gimp2, pango or cairo

Reported by: mdugdale@… Owned by: mij@…
Priority: Normal Milestone:
Component: ports Version: 1.2
Keywords: Cc: rhwood@…, lodea@…
Port:

Description

Hello. I'm running in a multi-user environment on which, for security reasons, I've recently had to set the default NSUmask to 27 (I'm not sure that this has anything to do with the problem, but it might). Not long after, updated run port -a upgrade, upgraded glib2 and cairo, and now gimp2 is broken.

I've tried uninstalling cairo and pango, but nothing seems to fix the problem.

some of the relevant active ports:

cairo @1.0.4_0 (active) gimp2 @2.2.10_0 (active) glib2 @2.10.1_1 (active) pango @1.12.0_0 (active)

the errors on trying to execute gimp are:

(gimp:2336): Pango-WARNING : No builtin or dynamically loaded modules were found. Pango will not work correctly. This probably means there was an error in the creation of:

'/opt/local/etc/pango/pango.modules'

You should create this file by running pango-querymodules.

(gimp:2336): Pango-WARNING : pango_shape called with bad font, expect ugly output

(gimp:2336): Pango-WARNING : pango_font_get_glyph_extents called with bad font, expect ugly output

(gimp:2336): Pango-CRITICAL : pango_cairo_show_glyph_string: assertion `PANGO_IS_CAIRO_FONT (font)' failed

(gimp:2336): Pango-CRITICAL : pango_cairo_show_glyph_string: assertion `PANGO_IS_CAIRO_FONT (font)' failed

(gimp:2336): Pango-CRITICAL : pango_cairo_show_glyph_string: assertion `PANGO_IS_CAIRO_FONT (font)' failed

(gimp:2336): Pango-CRITICAL : pango_cairo_show_glyph_string: assertion `PANGO_IS_CAIRO_FONT (font)' failed

(gimp:2336): Pango-CRITICAL : pango_cairo_show_glyph_string: assertion `PANGO_IS_CAIRO_FONT (font)' failed

(script-fu:2338): LibGimpBase-WARNING : script-fu: wire_read(): error

Cheers

Change History (4)

comment:1 Changed 15 years ago by lodea@…

Cc: lodea@… added

I have encountered two problems with Pango while trying to get ethereal working on my MacBook Pro. The first is a simple error in the portfile. In the post-destroot target is the line:

${destroot}${prefix}/bin/pango-querymodules ${destroot}${prefix}/lib/pango/1.4.0/modules/* >${destroot}${prefix}/etc/pango/pango.modules"

The version number should be 1.5.0, and as a result of this, the pango modules file is always empty. The other problem with this line, is it also catches the .lo files in that directory. So it should be:

${destroot}${prefix}/bin/pango-querymodules ${destroot}${prefix}/lib/pango/1.5.0/modules/*.so >${destroot}${prefix}/etc/pango/pango.modules"

However, even after my pango.modules file had all the modules listed, I continued to get "No builtin or dynamically loaded modules were found" when starting ethereal (and ethereal would sigbus as before). My best guess is that this is some problem with dynamic loading on intel. So to work around it, I built pango with all the modules statically linked in. To do this, add

--with-included-modules=yes --with-dynamic-modules=no

to pango's configure.args.

With these changes, ethereal is now working for me.

comment:2 Changed 15 years ago by darwin@…

(In reply to comment #1)

However, even after my pango.modules file had all the modules listed, I continued to get "No builtin or dynamically loaded modules were found" when starting ethereal (and ethereal would sigbus as before). My best guess is that this is some problem with dynamic loading on intel.

On my PPC G4, I get the same behavior. That's not an intel specific problem.

In fact, with gtk2 and pango, I realized that the binaries which detect modules use a define (SOEXT) which is mapped on ".dylib". So I modified libtool to get them with a dylib extension. After that patch, generation of pango.modules and gtk.modules works. However, I still get the "No builtin or dynamically loaded modules were found" only for pango.

Hope this helps ? Cheers

comment:3 Changed 14 years ago by rhwood@…

Cc: rhwood@… added
Owner: changed from darwinports-bugs@… to mij@…

comment:4 Changed 14 years ago by mdugdale@…

Resolution: fixed
Status: newclosed

It now all worksforme with pango @1.12.1_0.

Cheers

Note: See TracTickets for help on using tickets.