Re: Gimp 2.2.6 and libpangocairo

[Florian Kulzer <florian@molphys.leidenuniv.nl>]

On Thu, Jul 20, 2006 at 20:38:09 -0600, DJ Hackenbruch wrote:
> Well, I tried a re-install of both (via apt-get) and looking in the 
> /usr/lib directory there is no such file named "libpangocairo" real or symb 
> link either. Do I have to make them? Link them to what?

Creating a symlink can indeed be an effective trick to get pre-compiled
non-Debian programs running. It should not be necessary to do this for a
standard Debian package such as gimp, though. I just checked with
apt-file: libpango1.0-0 and libpango1.0-dev are the only two packages
which contain any "libpangocairo..." files. (I have stable, testing and
unstable in my sources.list.) Are you using an official Debian package
for the Gimp?

Another thing which might help you to figure out what goes wrong is to
use "ldd" to see the exact name and version of the library that Gimp was
linked against:

$ ldd $(which gimp) | egrep 'pango|cairo'
        libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb7a32000)
        libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb799e000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb78b3000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb7879000)

(My example is for gimp 2.2.12-1 on Sid.)

I am a bit confused because you really should not have that kind of
problem on Sarge. Can you post the output of "apt-cache policy gimp"?

-- 
Regards,
          Florian