Ethereal starts up with GLib-GObject-CRITICAL errors

[ideinit@…]

Ethereal (0.10.14_0+darwin_8) was built with the follwing dependencies:

glib2 @2.8.6_0 gtk 2@2.8.12_1+darwin_8 openssl @0.9.8_1 libpcap @0.9.4_0 zlib @1.2.3_0

When I ran it, it gave the following warning and errors:

---

sudo ethereal

(ethereal:3586): GLib-GObject-WARNING : Two different plugins tried to register 'BasicEngineFc'.

(ethereal:3586): GLib-GObject-CRITICAL : g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed Failed to load Pango module for id: 'BasicScriptEngineFc' (ethereal:3586): GLib-GObject-WARNING : Two different plugins tried to register 'BasicEngineFc'.

---

the warnings/errors continue to repeat as I use ethereal, but doesn't seem to affect the functionality of ethereal itself.

Did I build ethereal against the wrong libraries?

[opendarwin.org@…]

Do you have any other DP installed things that use gtk2? If so, do they show the same error?

[ideinit@…]

(In reply to comment #1)

Do you have any other DP installed things that use gtk2? If so, do they show the same error?

No I do not have other DP that uses gtk2 that I can test with. But I do not have this error with ethereal on another OS X machine with older versions glib2 and gtk2.

[ideinit@…]

(In reply to comment #1)

Do you have any other DP installed things that use gtk2? If so, do they show the same error?

Ok, I was wrong, etherape indirectly depends on gtk2: etherape -> libgnomeui -> gtk2

It has the same error and MORE:

sudo etherape -i en1 Password:

(etherape:4288): GLib-GObject-WARNING : g_object_set_property: object class GtkFrame' has no property named orientation'

(etherape:4288): GLib-GObject-WARNING : Two different plugins tried to register 'BasicEngineFc'.

(etherape:4288): GLib-GObject-CRITICAL : g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed Failed to load Pango module for id: 'BasicScriptEngineFc' (etherape:4288): GLib-GObject-WARNING : Two different plugins tried to register 'BasicEngineFc'.

[...]

[ideinit@…]

The problem turned out to be a corrupted pango.module file, as outlined in this thread: ​http://www.opendarwin.org/pipermail/darwinports/2005-October/029039.html

where there were two entries for "/opt/local/lib/pango/1.4.0/modules/pango-basic-fc.so BasicScriptEngineFc ...". I have no idea how pango.module got to that state... perhaps due to an upgrade??

The fix was simply a reinstall of pango and everything was okay.