Bug 145640 - GIMP does not recognize correct freetype version
GIMP does not recognize correct freetype version
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: gimp (Show other bugs)
3
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Nils Philippsen
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-20 06:57 EST by Jouni Väliaho
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-20 11:41:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jouni Väliaho 2005-01-20 06:57:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20050109 Fedora/1.7.5-3

Description of problem:
After recent update of GIMP I failed to launch it on GNOME menu.
The GIMP Message window opens and it contains following message:

FreeType version too old!

The GIMP requires FreeType version 2.1.7 or later.
Installed FreeType version is 2.1.5.

Somehow you or your software packager managed
to install The GIMP with an older FreeType version.

Please upgrade to FreeType version 2.1.7 or later.


I have following freetype packages installed (rpm -qa | grep freetype):
freetype-2.1.9-1
freetype-demos-2.1.9-1
freetype-devel-2.1.9-1
freetype-utils-2.1.9-1
and I have flowwing gimp packages ()
gimp-print-utils-4.2.7-2
gimp-print-4.2.7-2
gimp-2.2.2-0.fc3.3



Version-Release number of selected component (if applicable):
gimp-2.2.2-0.fc3.3

How reproducible:
Always

Steps to Reproduce:
1. Click on the Start button (red hat)
2. Select Graphics
3. Select The Gimp
    

Actual Results:  GIMP Message window appears. After a click on OK, it
dissapears, and 
the Gimp is never launched.

Expected Results:  The Gimp launches properly.

Additional info:
Comment 1 Nils Philippsen 2005-01-20 09:07:33 EST
Perhaps you have some stray old version of freetype lying around... What does
the command "ldd /usr/bin/gimp-2.2" give?
Comment 2 Jouni Väliaho 2005-01-20 10:42:53 EST
ldd /usr/bin/gimp-2.2 gives:
        libgimpwidgets-2.0.so.0 => /usr/lib/libgimpwidgets-2.0.so.0
(0x00de6000)
        libgimpcolor-2.0.so.0 => /usr/lib/libgimpcolor-2.0.so.0
(0x00556000)
        libgimpmodule-2.0.so.0 => /usr/lib/libgimpmodule-2.0.so.0
(0x00561000)
        libgimpbase-2.0.so.0 => /usr/lib/libgimpbase-2.0.so.0 (0x00547000)
        libgimpthumb-2.0.so.0 => /usr/lib/libgimpthumb-2.0.so.0
(0x00510000)
        libgimpmath-2.0.so.0 => /usr/lib/libgimpmath-2.0.so.0 (0x00509000)
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x00111000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00edc000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00c85000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0
(0x003c6000)
        libm.so.6 => /lib/tls/libm.so.6 (0x0085e000)
        libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x007a5000)
        libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x00d08000)
        libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0x00d15000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x003db000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00ca1000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00aaa000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00aa5000)
        libdl.so.2 => /lib/libdl.so.2 (0x00883000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00a14000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00401000)
        libfreetype.so.6 => /usr/local/lib/libfreetype.so.6 (0x00ba3000)
        libz.so.1 => /usr/lib/libz.so.1 (0x00962000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00974000)
        libc.so.6 => /lib/tls/libc.so.6 (0x00566000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00889000)
        libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x009ff000)
        libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x00427000)
        libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0x00a0f000)
        libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x00523000)
        libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x00a04000)
        libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x009cd000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x00952000)
        /lib/ld-linux.so.2 (0x00719000)
        libexpat.so.0 => /usr/lib/libexpat.so.0 (0x009ac000)
Comment 3 Nils Philippsen 2005-01-20 11:41:32 EST
Look at this:

libfreetype.so.6 => /usr/local/lib/libfreetype.so.6 (0x00ba3000)

--> you're not using the packaged version of freetype (but some older version
installed into /usr/local). Ensure that:

- either there is no mention of /usr/local/lib in /etc/ld.so.conf (or the files
in /etc/ld.so.conf.d)
- or /usr/lib is mentioned before /usr/local/lib

Note You need to log in before you can comment on or make changes to this bug.