GIMP 3.0 Released

[Tenoch]

Their AppImage did not work on fossapup64 version 9.5, released Sep 2020, however I've no idea if we are talking about library incompatibility or bugs

https://www.gimp.org/downloads/

[hikohan]

launch GIMP3 AppImage get error:

ERROR: appimage_is_terminal_app : sqfs_open_image error: /u/tool/Appimage/Applications/GIMP-3.0.0-x86_64_ad816dbfed72a5043f7c1b7e8c1b41f7.AppImage
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_register_in_system : sqfs_open_image error: /u/tool/Appimage/Applications/GIMP-3.0.0-x86_64_ad816dbfed72a5043f7c1b7e8c1b41f7.AppImag

AppImage was built using the zstd zlib

Upgrade AppImage launcher or convert image from zstd to xz, maybe works.

Thanks for the GIMP3 info.

[bigpup]

Appimage works in BookwormPup64 10.0.10

[Jasper]

@Tenoch

The latest build of GIMP requires Glib 2.35 and Python 3.11.

Screenshot-20250319T071551.webp (14.84 KiB) Viewed 439 times

[bugnaw333]

Works in EasyOS.

[gychang]

AppImage works in the latest vanillaDpup64-xwayland10.0.74iso.

screenshot.f7bpBJGTRl.png (19.49 KiB) Viewed 400 times

[step]

Release notes page: https://www.gimp.org/release-notes/gimp-3.0.html

3.0 is built on GTK3: another nail in the GTK2 coffin. Unfortunately the appimage doesn't work on Fatdog64-903. It starts but then hangs without displaying the GIMP GUI, and one has to kill the appimage.

[mikewalsh]

Yup. +1 on the GTK3 stuff.....and Jasper's info probably doesn't help, either. Most of my "kennels" are around the glibc 2.28-2.31 range.

For myself, I doubt I shall bother upgrading. The v2.10.25 AppImage (from HERE) does everything I could possibly want from it, so I'll be sticking with that for the forseeable future...

This is the one used in the GIMP-portable package.

Mike.

[step]

Yeah, I use the 2.10.25 appimage on Fatdog64 too, even though the repo carries a newer package, 2.10.32, and the official 2.10 series EOL version is 2.10.38. I prefer the older appimage because it includes some plugins I use.

[p310don]

Appimage works for me in Fatdog

Not sure what's different @step between yours and my setup, but seems ok.

[step]

To make GIMP 3.0 work on my Fatdog64 system I must run:

Code: Select all

env -u LD_LIBRARY_PATH ./GIMP-3.0.0-x86_64.AppImage      # unset LD_LIBRARY_PATH to run

However, this doesn't work:

Code: Select all

env LD_LIBRARY_PATH="/lib64:/usr/lib64:/usr/local/lib64" ./GIMP-3.0.0-x86_64.AppImage

What puzzles me is the latter LD_LIBRARY_PATH value is taken from the default /etc/profile file. Indeed GIMP 3.0 doesn't run on my rig even if I boot without savefile. I really need to unset LD_LIBRARY_PATH for 3.0 to work.

@p310don if you open a terminal, run GIMP 3.0 from the shell prompt then echo $LD_LIBRARY_PATH, what do get?

[mikewalsh]

@step :-

Just to add to this discussion, I've put together a GIMP 3.0 'portable' build using the official AppImage. It does only run for me in BWP64 - this being the newest kennel resident I have ATM. You're welcome to try it if you want, but it's a humungous, full half-gigabyte in size:-

viewtopic.php?p=145421#p145421

TBH, I don't like the layout. The GIMP team moved from the older, traditional "look" of GIMP 2.8 to a semi-'flat' appearance with GIMP 2.10.....and with the release of GIMP 3.0, they've fully-embraced the awful "flat look". And I HATE it!

Up to you, of course!

Mike.

[step]

@mikewalsh thanks, I tried your portable but it needs the same trick as the official appimage to run on my system: env -u LD_LIBRARY_PATH ./LAUNCH &.

I've been using 2.10 for some time, so I don't mind the flat appearance; but I dislike dark themes.

[wiak]

Looking at the screenshot of Gimp 3.0, I can only say I wish they would change it to be a bit more like Krita, which I find much easier to use because of the way it is presented. However, Gimp is pretty good and no doubt very good if you take the time to learn it well. Actually, vector-graphics-based Inkscape has been improving of late, especially for purposes such as creating structured diagrams including flowcharts, both of these needing decent method of drawing constructor lines with arrows such that moving blocks around also dynamically moves the connectors. Version 1.1 was still crap for that purpose, but 1.4 finally becoming good at it.

As far as Gimp type bitmap processing comparison goes, the Krita interface, at a simple level, is a little bit similar (in look and feel) to newer Inkscape arrangements, but Gimp still sticks to these floating panels and (to me at least) unfamiliar tool and function arrangements. Nothing beats mtpaint in odd arrangement though... though I do actually use mtpaint quite a lot for one or two of its functions such as Crop and Scale image, which both work simply and efficiently.

Other than for these mtpaint functions I certainly previously tended to use Gimp for rasterised image work, but I am definitely now moving more towards using Krita for bitmap/raster/photograph type processing. I also rely a lot on Okular for pdf processing so plenty KDE libs on my system generally anyway.

Overall though, full Inkscape is more important to me than Gimp or Krita since what I make tends to be more appropriately scalable vector graphics based and so I tend to put in a lot of effort keeping my skills up in terms of using Inkscape.

Most Gimp experts, being those who use it most every day, will however no doubt be celebrating any new Gimp and intimately know exactly why it is better than any older ones.

[Grey]

I finally got to the third version Of course, I had to change the interface in the settings so that the icons and labels were normal in size and colors. For some reason, the translation into my native language changed and it became unclear where the previous functions were. And I switched to English because it turned out to be clearer that way. Otherwise, it seems to be fine so far, the necessary filters seem to be working.
I am currently enabling single window mode in the menu so that parts of the interface are not scattered all over the screen. I'm getting old.

[p310don]

@step

Running GIMP from terminal doesn't work. Running it from a click on the appimage does. No idea why the difference.

With GIMP running, doing this:

Code: Select all

echo $LD_LIBRARY_PATH

gives this output:

Code: Select all

/lib64:/usr/lib64:/usr/local/lib64:/usr/lib64/firefox:/usr/lib64/seamonkey:/lib:/usr/lib:/lib32:/usr/lib32:/usr/local/lib:/usr/local/lib32:/opt/qt5/lib64