Tumbleweed - Gimp-3, Will not start from Start Menu, .desktop file issue, Tools panel crashes
All, Just tried to start gimp-3 for the first time and starting from the menu Graphics->Image Editing->Gimp doesn't do anything. This is apparently due to the prior desktop files have gimp-2.10 in them and now its gimp-3.0. Ended up starting from the command line, but the tools panel crashes on resize. Just become unresponsive and completely transparent. I was able to crop and image, but crop no longer displays the crop-size when resizing the crop window unless the origin corresponds to 0,0 of the image. You just get the current cursor position displayed in the status bar (not real helpful when trying to crop an image to a particular size not starting at 0,0) Is there going to be a gimp-2 version preserved? It is quite apparent that gimp-3 attempt to port to gtk3/4 is not fully baked. The tools no longer fit in the tools panel and take about 150% of the space the gimp-2 tools did. The "Export As" png options dialog is all misaligned and looks like all the check-boxes just got crammed together in a box at the bottom. Is this fixable? What to do about the .desktop files? Any custom menu entries are broken. why not just change to using "gimp"? Let the symlink in /usr/bin from gimp->gimp-3.0 take care of it? -- David C. Rankin, J.D.,P.E.
On 3/16/25 2:47 AM, David C. Rankin wrote:
These were the errors dumped to stderr: (gimp:178973): Gtk-WARNING **: 02:28:35.225: Calling org.freedesktop.portal.Inhibit.Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Inhibit” on object at path /org/freedesktop/portal/desktop (gimp:178973): Gtk-CRITICAL **: 02:31:21.102: gtk_file_chooser_set_current_folder_file: assertion 'G_IS_FILE (file)' failed (gimp:178973): GLib-GObject-CRITICAL **: 02:31:21.102: g_object_unref: assertion 'G_IS_OBJECT (object)' failed -- David C. Rankin, J.D.,P.E.
On 3/16/25 2:49 AM, David C. Rankin wrote:
forget it, gimp-3 is horrid and the port to a new toolkit is half-baked. I reinstalled 2.10 and locked gimp. Works so much better, the menu entries work again and the interface is so much cleaner. Save your gimp-2.10, libgimp-2_0-0, and libgimpui-2_0-0 rpms if you have them. You'll wish you had later... -- David C. Rankin, J.D.,P.E.
David C. Rankin composed on 2025-03-16 03:18 (UTC-0500):
Save your gimp-2.10, libgimp-2_0-0, and libgimpui-2_0-0 rpms if you have them. You'll wish you had later...
I have a TW .iso from last September that has 2.10. :) -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 3/16/25 01:18, David C. Rankin wrote:
Save your gimp-2.10, libgimp-2_0-0, and libgimpui-2_0-0 rpms if you have them.
I'm a simpleton, which is why I still use "xv" for my, seldom needed, graphics manipulations. Basically I might go in change the resolution, aspect, or crop something.
On 3/16/25 08:28, Bill Swisher wrote:
I'm a simpleton too! While I've used and appreciated GIMP, I've also been using and appreciating xv since 1990! It's one of the first programs I install for my users when I set up a system. It's also useful for testing X11 port forwarding. Its longevity is remarkable, I first used it on a SunOS UNIX network before Linux. There should be a Hall of Fame where programmers like John Bradley can be honored. Regards, Lew
On 3/16/25 10:05, Lew Wolfgang wrote:
Its longevity is remarkable, I first used it on a SunOS UNIX network before Linux.
Yeah, that's where I first discovered it. We had some SPARC's laying around not being used much, our workhorses were DEC VAX/VMS, the "Windows" computers we had didn't do much in the way of networking at the time, found something out of Australia that would allow them to do TCP/IP.
On Sunday, 16 March 2025 at 04:18:22 am GMT-4, David C. Rankin <drankinatty@gmail.com> wrote: ... forget it, gimp-3 is horrid and the port to a new toolkit is half-baked. I reinstalled 2.10 and locked gimp. Works so much better, the menu entries work again and the interface is so much cleaner. Save your gimp-2.10, libgimp-2_0-0, and libgimpui-2_0-0 rpms if you have them. You'll wish you had later... ** I have gimp3 which opens and runs fine, usable, but seldom used. fwiw -- tj
On 3/16/25 11:46 AM, Tom Jones wrote:
I'm sure it will get better, right now Tumbleweed is pushing a RC3 package?? The Gtk-CRITICAL and GLib-GObject-CRITICAL errors I experience with the crash of the tools window shows there is still a bit of work to do (I use separate tools, image and layers, paths, history windows, not the Windows->Single Window Mode setup) If you have a desktop, with 24" monitor, gimp3 may be usable, but the gtk+2 -> gtk+3 update for gimp was always going to be a heavy lift and somewhat of a hodgepodge. Gtk+3 removed widgets Gimp relies on to work (e.g. the ruler-widget, the toolbar widge, etc.) Gtk3 also went from a traditional Linux UI to the ham-fisted .css theme model so Gnome would (supposedly) render on a tablet as well as a desktop and then Gnome spent a decade breaking theme backwards compatibility with each prior point-release until a majority of theme designers threw in the towel. Foreseeably, Gnome on phones and tablets never materialized but we are left with that legacy in Gtk so that now all gtk apps look about as exciting as milk-toast. In this whole kerfuffle, the biggest loss was control over element placement and size. Which is why when I used "Export As" on my laptop, the dialog with all the export options was a holy mess with all options crammed together in a vbox near the bottom of the dialog without any consistent alignment. Icon size is also a crap-shoot due to CSS .margin and .padding defaults resulting in differing renderings. And no, ported apps rarely take the time to set .margin and .padding for each list, icon group, etc.. so what you get is often like the proverbial "Box of Chocolates". I'm sure the same "Export As" dialog would rendered completely differently at 2560x1600, but at 1600x900 it is a mess. There is a long history of tension in Gnome's co-opting of Gtk (the Gimp Toolkit) for it's own. This appears to be the latest messy chapter. (search the history, it's a pretty good read) We will see where this goes, but I doubt it ends well. There is just no way to make Gtk+3/4 look as good as Gtk+2 did. One was envisioned as a semi-generic user interface now tightly coupled with Gnome's libadwaita, the other was a programmer's toolkit for creating Linux desktop applications in C. I've yet to see a toolkit that does both well. Interesting note, Archlinux is still on Gimp-2.10. It only packages stable upstream releases. Tumbleweed should do the same. Release-Candidates should not be packaged and distributed as if they were part of a stable release. The are not. That's why there is a RC in the name. I recall a similar rush to package 'a' quality software as if it were a release. (KDE 4.04-a) That didn't end will either :) But openSUSE 11.0 (the first openSUSE release) did go on to be a very good release. (after going back to the last stable KDE) Here is hoping Gimp-3 gets all the kinks worked out. "sudo zypper al gimp libgimp-2_0 libgimpui-2_0" is just a bit of insurance to tide me over until it does.... -- David C. Rankin, J.D.,P.E.
participants (5)
-
Bill Swisher -
David C. Rankin -
Felix Miata -
Lew Wolfgang -
Tom Jones