> The problem is something to do with dynamic linking. I am sure of that.
> When imlib can't load an image with one of the compiled in image
> libraries, it falls back on the imagemagick or netpbm. If imlib fails to
> dynamically load the image loading code for example, this is a case when
> it will fall back on imagemagick.
>
> I don't see this problem on my system, so am not sure what is causing it.
I've seen this probelm as well, and I did trace it through all of the
gnome libraries. What you say is basically correct. It tries to load
an imlib shared library, this succeeds, but it it is unable to find a
symbol in that library that it needs (although the symbol does exist).
It then falls back to converting the image by forking imagemagick and
piping data there and back, which is slow...
Again this only happens when using themes and as far as I can tell only
when using a theme that uses the pixmap engine. Depending on the theme
or version of software, phase of the moon, whatever, you get different
effects depending on which shared library is affected.
To summarize there are three problems that seem to be related:
1. Slowness. Everything appears to work, but is very slow compared
to other gnome apps.
2. You get 'convert: Color is not known to X server ' messages plus
lots of garbage, but it otherwise appears to work.
3. You get 'undefined symbol: gdk_display' and the app won't even
start.
Has anyone seen any of these problems when not using a pixmap based theme?
Themes such as ThinIce that use a different engine are fine.
..Steve
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
