"Olivier Lecarme" <[EMAIL PROTECTED]> writes:
> >abort? I've never heard about that problem before, seems to be OSF1
> Probably, but I don't understand it. Maybe this comes from one
> specificity of OSF1, i.e. libc.so is in /usr/shlib, not in /usr/lib. The
> "abort" entry point is mentioned in libglib-2.0.so. Maybe the fix should
> occur in the glib configuration ?
you should try to run the tests that come with the glib-2.0 tarball.
If you get problems there you should definitely report them using
bugzilla.gnome.org against the glib module.
> >you should install a suitable XftConfig file to make the text tool happy.
> >On the other hand since the text tool is almost unuseable it's not that
> I must confess I don't even know what XftConfig is...
the font configuration for Xft, the next-generation X font rendering.
The text tool uses it since PangoFT2 shares the configuration file
with the Xft backend. This means you need to configure Xft even though
your X server doesn't have support for it.
> >I'd suggest you temporarily move the plug-ins directory away and check
> >if gimp works w/o any plug-ins. If that works you could reinstall some
> >simpler plug-ins and test them. Perhaps only script-fu is broken for
> I did exactly that. Finally, only script-fu seems to be broken. I get
> some unaligned accesses, maybe because the Alpha is a true 64-bit
we definitely need to fix this problem. Could you please file a
bug-report for it at bugs.gimp.org?
Gimp-developer mailing list