Which are the files responsible for the menu on Gimp 2.6?

[kromak]

Hello. I am currently trying to make a Gimp 2.6.8 install to work on another Linux distros. First I copied the gimp binary file. It complained about not having a gegl lib. I copied it from my distro. It worked, nonetheless, Gimp continued to complain about other library files. I continued to copy all the necessary files until the executable Gimp file worked.

However it was seriously handicapped. I then copied the .gimp dir that was on my home/user. It may improved it in someways, but not enough. The brushes still were not working, even though they were on .gimp as far as know. Somehow I figured out that there was a /usr/share/gimp directory full of files and subdirs. Copied it to the newer Linux distro. The brushes started to work. Now Gimp was close to reach a functional state.

Despite that, there still are two issues. The first is that, since it was not properly installed, I cannot click on a image file and select it to be opened by Gimp. I tried to understand how to select a random program to open a certain file type, but at least until now, was not able to do so. However, this is a distro specific issue and so not to be treated here.

The second is that the menu (file,edit,etc) is not showing up. So I believe that there still are some configuration files that I did not copy to the newer distro. Hence, I would deeply appreciate if someone can point the files responsible for such part of Gimp. Or whatever is necessary to solve this issue. If one does not know the specific files, yet has a good idea of existing gimp config files, it copy all at once.

Thanks for reading all that.

[Ofnuts]

Try /usr/share/gimp/2.0/menus/image-menu.xml (and actually everything in /usr/share/gimp/2.0/menus/).

AFAIK all of Gimp is in /usr/bin (main executables), /usr/lib/gimp/2.0/ (plugins) and /usr/share/gimp/2.0/ (most of the data)

[rich2005]

If not able to fix your installation then there are Gimp 2.6 packages for ubuntu distributions here:
https://launchpad.net/~malcscott/+archiv.../+packages

I did try using the PPA for a regular install in a Ubuntu 16.04 (virtual machine) but ran into update / dependency issues. However downloading the relevant packages and installing manually (sudo dpkg -i *.deb) worked. With a caveat, some warning messages: screenshot: https://i.imgur.com/ZcKwKAS.jpg

Warning messages apart, it seems to work although no real testing for whoopsies. screenshot: https://i.imgur.com/NeTwfv0.jpg

[kromak]

(01-02-2020, 04:35 PM)Ofnuts Wrote: Try /usr/share/gimp/2.0/menus/image-menu.xml (and actually everything in /usr/share/gimp/2.0/menus/).

AFAIK all of Gimp is in /usr/bin (main executables), /usr/lib/gimp/2.0/ (plugins) and /usr/share/gimp/2.0/ (most of the data)

I already did copy it, as I said before

Quote:Somehow I figured out that there was a /usr/share/gimp directory full of files and subdirs. Copied it to the newer Linux distro

Nonetheless, I did something wrong as the menus were not working. However I had to repeat the process and now it's working. However, when I try to open a jpeg or a png gimp says

Quote:Opening '/media/ubuntu-mate/ea4c087e-2e07-4b60-8199-2ece22830238/imagens/acessorios letras-P/0eem index.png' failed:

Unknown file type

Any ideas? In the meanwhile, will try rich2005's method

[Ofnuts]

You need the file-* executables in one of the plug-ins directory. You can check the contents of the pluginrc in your Gimp profile to see if they are listed. You  should have something like:

Code:

(plug-in-def "/usr/lib/gimp/2.0/plug-ins/file-png" 1494589443
   (proc-def "file-png-load" 1
        "Loads files in PNG file format"
        "This plug-in loads Portable Network Graphics (PNG) files."
        "Michael Sweet <mike@easysw.com>, Daniel Skarda <0rfelyus@atrey.karlin.mff.cuni.cz>"
        "Michael Sweet <mike@easysw.com>, Daniel Skarda <0rfelyus@atrey.karlin.mff.cuni.cz>, Nick Lamb <njl195@zepler.org.uk>"
        "1.3.4 - 03 September 2002"
        "PNG image"
        0
       (icon stock-id -1 "")
       (load-proc
           (extension "png")
           (magic "0,string,‰PNG\r\n\032\n")
           (mime-type "image/png"))
        ""
        3 1
       (proc-arg 0 "run-mode" "The run mode { RUN-INTERACTIVE (0), RUN-NONINTERACTIVE (1) }")
       (proc-arg 4 "filename" "The name of the file to load")
       (proc-arg 4 "raw-filename" "The name of the file to load")
       (proc-arg 13 "image" "Output image"))

[kromak]

(01-06-2020, 01:46 AM)Ofnuts Wrote: You need the file-* executables in one of the plug-ins directory. You can check the contents of the pluginrc in your Gimp profile to see if they are listed. You  should have something like:

Code:

(plug-in-def "/usr/lib/gimp/2.0/plug-ins/file-png" 1494589443
   (proc-def "file-png-load" 1
        "Loads files in PNG file format"
        "This plug-in loads Portable Network Graphics (PNG) files."
        "Michael Sweet <mike@easysw.com>, Daniel Skarda <0rfelyus@atrey.karlin.mff.cuni.cz>"
        "Michael Sweet <mike@easysw.com>, Daniel Skarda <0rfelyus@atrey.karlin.mff.cuni.cz>, Nick Lamb <njl195@zepler.org.uk>"
        "1.3.4 - 03 September 2002"
        "PNG image"
        0
       (icon stock-id -1 "")
       (load-proc
           (extension "png")
           (magic "0,string,‰PNG\r\n\032\n")
           (mime-type "image/png"))
        ""
        3 1
       (proc-arg 0 "run-mode" "The run mode { RUN-INTERACTIVE (0), RUN-NONINTERACTIVE (1) }")
       (proc-arg 4 "filename" "The name of the file to load")
       (proc-arg 4 "raw-filename" "The name of the file to load")
       (proc-arg 13 "image" "Output image"))

I had copied my entire .gimp from the other Linux distro , and hence the pluginrc file from there.

It had things like:

Code:

(plug-in-def "/usr/lib/gimp/2.0/plug-ins/file-jpeg" 1354823336

However, I did not copy my /usr/lib/gimp dir from the other distro.

When I run gimp, it erases it and creates a new pluginrc without nothing on it.

I decided to first copy my entire /usr/lib/gimp from the other distro to /usr/lib and test it with the pluginrc from the other distro.

When I did that, countless error messages appeared. These are the first one third or similar.

Code:

../../../../glib/goption.c:2393: ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in entry (null):debug-handlers
LibGimpModule-Message: 17:47:34.908: Module '/usr/lib/gimp/2.0/modules/libcolor-selector-cmyk.so' load error: liblcms.so.1: cannot open shared object file: No such file or directory
LibGimpModule-Message: 17:47:34.909: Module '/usr/lib/gimp/2.0/modules/libdisplay-filter-proof.so' load error: liblcms.so.1: cannot open shared object file: No such file or directory
LibGimpModule-Message: 17:47:34.913: Module '/usr/lib/gimp/2.0/modules/libdisplay-filter-lcms.so' load error: liblcms.so.1: cannot open shared object file: No such file or directory
LibGimpModule-Message: 17:47:34.919: Module '/usr/lib/gimp/2.0/modules/libcontroller-linux-input.so' load error: libhal.so.1: cannot open shared object file: No such file or directory
/usr/lib/gimp/2.0/plug-ins/file-mng: error while loading shared libraries: libmng.so.1: cannot open shared object file: No such file or directory

(gimp-2.6:4316): LibGimpBase-WARNING **: 17:47:35.985: gimp-2.6: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/file-tiff-load: error while loading shared libraries: libtiff.so.4: cannot open shared object file: No such file or directory

(gimp-2.6:4316): LibGimpBase-WARNING **: 17:47:36.226: gimp-2.6: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/file-xjt: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

(gimp-2.6:4316): LibGimpBase-WARNING **: 17:47:36.316: gimp-2.6: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/help-browser: error while loading shared libraries: libwebkit-1.0.so.2: cannot open shared object file: No such file or directory

(gimp-2.6:4316): LibGimpBase-WARNING **: 17:47:36.373: gimp-2.6: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/file-jpeg: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

[rich2005]

Quote:..I decided to first copy my entire /usr/lib/gimp from the other distro to /usr/lib and test it with the pluginrc from the other distro.

Ofnuts might have some good advice.

However, I doubt if it will be as easy as that. For I example I run a (sort of) portable Gimp 2.8 in my kubuntu 18.04 which has Gimp 2.10.14 installed. Lots and lots of tracking down compatible library files to get it working.

Just out of interest, which is the 'new' version of linux are you using?

[Ofnuts]

(01-11-2020, 05:54 PM)kromak Wrote: I had copied my entire .gimp from the other Linux distro , and hence the pluginrc file from there.

It had things like:

Code:

(plug-in-def "/usr/lib/gimp/2.0/plug-ins/file-jpeg" 1354823336

However, I did not copy my /usr/lib/gimp dir from the other distro.

When I run gimp, it erases it and creates a new pluginrc without nothing on it.

I decided to first copy my entire /usr/lib/gimp from the other distro to /usr/lib and test it with the pluginrc from the other distro.

When I did that, countless error messages appeared. These are the first one third or similar.

Code:

../../../../glib/goption.c:2393: ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in entry (null):debug-handlers
LibGimpModule-Message: 17:47:34.908: Module '/usr/lib/gimp/2.0/modules/libcolor-selector-cmyk.so' load error: liblcms.so.1: cannot open shared object file: No such file or directory
LibGimpModule-Message: 17:47:34.909: Module '/usr/lib/gimp/2.0/modules/libdisplay-filter-proof.so' load error: liblcms.so.1: cannot open shared object file: No such file or directory
LibGimpModule-Message: 17:47:34.913: Module '/usr/lib/gimp/2.0/modules/libdisplay-filter-lcms.so' load error: liblcms.so.1: cannot open shared object file: No such file or directory
LibGimpModule-Message: 17:47:34.919: Module '/usr/lib/gimp/2.0/modules/libcontroller-linux-input.so' load error: libhal.so.1: cannot open shared object file: No such file or directory
/usr/lib/gimp/2.0/plug-ins/file-mng: error while loading shared libraries: libmng.so.1: cannot open shared object file: No such file or directory

(gimp-2.6:4316): LibGimpBase-WARNING **: 17:47:35.985: gimp-2.6: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/file-tiff-load: error while loading shared libraries: libtiff.so.4: cannot open shared object file: No such file or directory

(gimp-2.6:4316): LibGimpBase-WARNING **: 17:47:36.226: gimp-2.6: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/file-xjt: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

(gimp-2.6:4316): LibGimpBase-WARNING **: 17:47:36.316: gimp-2.6: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/help-browser: error while loading shared libraries: libwebkit-1.0.so.2: cannot open shared object file: No such file or directory

(gimp-2.6:4316): LibGimpBase-WARNING **: 17:47:36.373: gimp-2.6: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/file-jpeg: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

This is why there are package managers... they handle this kind of dependency chains for you.

Something that could work, or at least reduce the work: install the current Gimp from your distro repo. This will drag in a lot of these libraries, hopefully upward compatible with the ones that your Gimp 2.6 needs. Thenre replace the Gimp executable and the Gimp trees in /usr/lib and /usr/share with the ones from your 2.6.

Another solution its to explain us why you must at all costs run Gimp 2.6 so we can figure out alternate solutions.

[kromak]

(01-11-2020, 06:45 PM)rich2005 Wrote: Just out of interest, which is the 'new' version of linux are you using?

Ubuntu 10.04

(01-11-2020, 08:33 PM)Ofnuts Wrote: This is why there are package managers... they handle this kind of dependency chains for you.

Something that could work, or at least reduce the work: install the current Gimp from your distro repo. This will drag in a lot of these libraries, hopefully upward compatible with the ones that your Gimp 2.6 needs. Thenre replace the Gimp executable and the Gimp trees in /usr/lib and /usr/share with the ones from your 2.6.

Another solution its to explain us why you must at all costs run Gimp 2.6 so we can figure out alternate solutions.

Interesting. I will try it after I try rich2005's first proposed solution.

I personally do not care about the Gimp's version, since I do not use it much and only to do mildly simple stuff. Nonetheless, my mother is a heavy user that does advanced editing and she does not accepts absolutely no substantial change to it. Once I tried a different Linux with a different Gimp and she complained endless about how it was awful, that the selection tool that she uses, for instance, to "soft" objects edges was different (and awful). Perhaps it was merely a matter of the brush of the newer gimp, but in another test, once again, I was not able to use the 2.6 brushes on other more recent Gimp.

I am also trying to compile gimp 2.6.0 and all its dependencies from the source in the last 3 or so years (although not continuously) but have been not able to do for a myriad of reasons, the last one being gimp's dependency on gtk 2.x headers. Gtk 2.x by its own, need to have pango compiled with support to X server. And I was not able to compile it because pango does not find the X11 headers. The fact that I compile and install all the dependencies outside common places like /usr/local/whatever does not help at all. I have been using things like PKG_CONFIG_PATH, LD_LIBRARY_PATH, LD_FLAGS, CPP_FLAGS, but on this case, none of these worked. However, I saw a topic on stack_overflow where they recommended to use CFLAGS. I did some preliminary test and it seems to be promising. However I changed the name of the directory where I was installing all of Gimp's dependencies, and it broke down all the .la and .pc files. Since I already had spent many dozens of hours in the previous weeks compiling the dependencies (facing many, many different issues doing that) I was just so tired that I decided to stop it and postpone the compiling attempt for a couple months and try other alternatives like this one.

[rich2005]

(01-21-2020, 12:33 AM)kromak Wrote: Ubuntu 10.04
Interesting. I will try it after I try rich2005's first proposed solution.

Not possible with that old version, You will need to upgrade to minimum 13.04 also packages for 14.04