Gimp complains about gtk+ version ("micro mismatch") when started from kmenu
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Gimp complains about gtk+ version ("micro mismatch") when started from kmenu
Hello all,
My Gimp has some issues when started from the KDE menu: It complains about the gtk+ version:
"Gtk+ version too old (micro mismatch)
GIMP requires GTK+ version 2.10.13 or later.
Installed GTK+ version is 2.10.9.
Somehow you or your software packager managed
to install GIMP with an older GTK+ version.
Please upgrade to GTK+ version 2.10.13 or later."
My libgtk2.0-0 package is at version 2.12.5-2, gimp is at version 2.4.4-1.
So I assume I HAVE "gtk+ 2.10.13 or later", and, in fact, gimp does start without any problems when invoked from commandline. Only when trying to start it from kmenu it provides me with the above dialog.
I tried to purge and reinstall gimp, with purging the .gimp-folder in the home-folder, and I just tried to reinstall kde, without any success ...
I'm using Debian lenny 2.6.22-3-686, with kde 3.5.8.
I have the same problem here.
Not only gimp isn't working, beryl-manager doesn't take the right GTK+ either.
Because I have too much time, I purged KDE, X.org, all libglib2, all GTKs and so on. Was a nice session ;-)
After reinstalling KDE, x.org, gimp and so on, it complains the wrong version again.
There is an libgtk-x11-2.0.so in /usr/lib and in /usr/local/lib
With
Code:
ldd $(which gimp) | grep gtk
I found out, that gimp is depending on the one in /usr/local/lib, but the one in /usr/lib is the file from the package libgtk2.0-0.
apt-file finds no information about the file in /usr/local/lib.
To make things worse, gimp noadays changed it's behaviour and doesn't start when invoked from commandline either, again with the mentioned popup dialog (i.e. before removing the libraries as olf suggested).
If I remove the above libraries, gimp then states (ldd ...) to depend on the libgtk-x11 libraries in /usr/lib/, but won't start, this time without any message. It shows the splash screen, but without the progression bar, and hangs. Clicking on the splash screen will cause it to disappear, but gimp still doesn't start.
dpkg-reconfiguring gimp oder libgtk2.0-2 after removing the libraries doesn't help either, gimp then fails to start (from bash) with the message "gimp: symbol lookup error: /usr/lib/libgtk-x11-2.0.so.0: undefined symbol: gdk_threads_add_idle".
So I moved those libraries back to the place I found them, and gave up so far.
After I thought really hard about neograndes reply, that there was no /usr/local/lib/libgtk in any of the Debian packages, I came up with the following solution:
I obviously compiled gtk+ myself once (although I don't remember ... keeping a rootlog suddenly seems to be a good idea ...). The version I compiled (533 days ago... why do I know? I used find -atime to find all the files) was 2.10.0. So I went to the gtk+ homepage, downloaded the source of 2.10.0, configured it ("./configure") and typed "sudo make uninstall" which got me rid of this gtk-version. A last "sudo ldconfig" (don't know whether this was necessery) and gimp started working again.
Now there's only another thing in /usr/local which I compiled the same day: metacity. I guess this selfcompiled version will not work anymore, but since I'm using KDE (and don't remember what I compiled metacity for) I don't care. I'm trying to uninstall this metacity the same way as the gtk+, but I didn't figure out yet which version it is.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.