[SOLVED] Problems on Gimp in latest Current

business_kid · 07-28-2019, 02:21 PM

Running on the Slackware64 Current of 16-Jul-2019 (except for mesa which is 19.1.3).

Gimp won't start. The message is

Code:

Libgimp version mismatch!

The GIMP binary cannot run with a libgimp version
other than its own. This is GIMP 2.10.12, but the
libgimp version is 2.10.10.

Maybe you have GIMP versions in both /usr and /usr/local

I don't have 2 versions. All the gimp libraries (not symlinks) are like this <libgimp-2.0.so.0.1000.10>. The gimp version is

Code:

bash-5.0$ gimp --version
GNU Image Manipulation Program version 2.10.12

Now I can and will revert to the current of April, because I still have that iso. This is a heads up for you guys.

EDIT: The version on the April version is identically named, but it works.

Code:

 bash-5.0$ gimp --version
GNU Image Manipulation Program version 2.10.10

ponce · 07-28-2019, 02:28 PM

strange, here gimp seems to start fine: what I have installed

Code:

$ grep libgimp-2.0.so /var/log/packages/gimp-2.10.12-x86_64-1 
usr/lib64/libgimp-2.0.so.0.1000.12

hitest · 07-28-2019, 02:33 PM

Quote:

Originally Posted by business_kid

Running on the Slackware64 Current of 16-Jul-2019 (except for mesa which is 19.1.3).
Gimp won't start.

Gimp is loading up fine here on an up to date version of Slackware64-current.

garpu · 07-28-2019, 03:05 PM

That's odd. I'm up to date on gimp, on current, and no problems. Maybe uninstall gimp's package and reinstall it?

Alien Bob · 07-28-2019, 04:17 PM

Did you recently abort a package installation or upgrade? You have files from both the old and the current gimp package on your system.

business_kid · 07-29-2019, 04:47 AM

I had the Gimp from the April ~Current. I did an upgradepkg (without the --reinstall or --install-new options) using the files in the July ~Current. To look at them, one would think they are the same package. But gimp --version from April reports version 2.10.10, whereas gimp from July reports gimp reports 2.10.12 :-/. The libraries from both appear identical. Was your source different? I'm on April's gimp now, and it's fine.

Alien Bob · 07-29-2019, 05:49 AM

Your system is broken, or your downloads are wonky. The July Gimp package is a different package than that of April.

allend · 07-29-2019, 07:11 AM

Quote:

The libraries from both appear identical

Not here (where gimp also works). After exploding the April and July packages in /tmp

Code:

bash-5.0$ md5sum -b /tmp/gimp-2.10.10-x86_64-1/usr/lib64/libgimp-2.0.so.0.1000.10; md5sum -b /tmp/gimp-2.10.12-x86_64-1/usr/lib64/libgimp-2.0.so.0.1000.12
0a7616453adb339322052913a831cb7f */tmp/gimp-2.10.10-x86_64-1/usr/lib64/libgimp-2.0.so.0.1000.10
4eb028e60cfb33c72698f76be252688f */tmp/gimp-2.10.12-x86_64-1/usr/lib64/libgimp-2.0.so.0.1000.12

business_kid · 07-29-2019, 09:38 AM

Quote:

Originally Posted by Alien Bob

Your system is broken, or your downloads are wonky. The July Gimp package is a different package than that of April.

Right that seems to settle it. I got the iso probably off heanet. I'll sort it out.

business_kid · 07-30-2019, 04:21 AM

Right.

I exploded my package, and gimp's 2.10.12 libraries are correct. So either my iso copy, or more likely my install ended funny - how, I dunno. I'm not going to lose sleep over it. There's been a lot of shifting and moving here, repartitioning and compiling. I'm not inclined to compile, shift, and repartition at the same time but I'm blaming it on that.