Heal selection doesn't show up in Enhancement menu

[bootchk]

Heal selection doesn't show up in Enhancement menu

[bootchk]

Thanks. Your analysis seems correct. I don't understand it either.

The Resynthesize menu item comes from resynthesizer_gui executable, which is written in C. The Heal Selection item comes from a Python script. All I can think of is that Python or PyGimp is not starting correctly. Note that Gimp only reads the Python plugins once, at startup. IOW, restarting Gimp is required after installing Python plugins. Please let me know whether that works.

I also considered that maybe something has changed in GIMP 2.9 but a quick search that others seem to be able to still use Resynthesizer with GIMP 2.9.

I am not familiar with Arch Linux. So I might need to read about pacman and the -git scripts, I don't know who wrote those, it is remotely possible they are flawed.

[jonnyrobbie]

Restarting gimp didn't help. I've tried deleting ~/.config/GIMP/2.9/pluginrc and restarting, but it didn't help. Starting gimp with --verbose flag: http://pastebin.com/b2CZyu5s

After that, I downgraded from gimp-git (2.9) to gimp stable (2.8) and the plugin now works fine. So it really is a problem with 2.9. I've read that devs are doing some substantioal things with gegl and maybe something changed about python too.

[bootchk]

Thanks. The trace from --verbose seems to indicate that gimp is trying to invoke 'python2', which cannot be found. Try entering that on a command line, or 'which python2', ('which' is a command that tells you how a command is resolved, the path to an executable, more or less.) Or you could test some other Gimp plugin written in Python (off the top of my head, I don't know whether any ship with Gimp.) I would guess that most linux distros have a symbolic link from python2 to some version of python executable. Could that link be missing? Possibly gimp should not be invoking 'python2', but just 'python' (I am not expert at python installations, they can be confusing especially with python3 etc.)

I am not familiar with gimp compatibility, but I would hope that for minor versions (2.9, etc.) they would not break external plugins. So I am dubious about the problem being in Gimp 2.9.

[jonnyrobbie]

$ which python; which python2; python --version; python2 --version
/usr/bin/python
/usr/bin/python2
Python 3.4.3
Python 2.7.10

[bootchk]

OK. I just searched and found your thread on reddit. There you say that the plugin .py scripts have a shebang of ....python2. But it seems like that is not the case in my git repository. So maybe gimp-git is changing them? In the shebang, does /usr/bin/env establish a different env than your personal env? Still thinking...

[bootchk]

In AUR gimp-git.git there is this:

 make DESTDIR="$pkgdir/" install
#  sed -i 's|#!/usr/bin/env python|#!/usr/bin/env python2|' "${pkgdir}"/usr/lib/gimp/2.0/plug-ins/*.py
 install -D -m644 "${srcdir}/linux.gpl" "${pkgdir}/usr/share/gimp/2.0/palettes/Linux.gpl"

i.e. gimp-git has a commented out line that was (?not in the latest version) mangling python to python2

I am not familiar with Arch, but this seems relevant.

[bootchk]

See this thread:

https://aur.archlinux.org/packages/gimp-git/

A snippet:

@mytbk: You may want to remove the line that's sedding out the

env python

from the PKGBUILD because specifying PYTHON=/usr/bin/python2 before the autogen.sh already takes care of converting the python interpreter (see the generated /usr/lib/gimp/2.0/interpreters/pygimp.interp after you build the package).

When the sed is performed, it prevents ALL of gimp's default python-based plugins from running. Peculiarly, scripts with the env python line left alone still execute fine. I found this out when I saw my Permute Layers plugin still around in gimp 2.9, but not the built-in openraster plugin for gimp.

[mytbk]

@bootchk It's aur/gimp-plugin-resynthesizer-git that sed the '/usr/bin/env python' to '/usr/bin/env python2'.

After I change python2 to python in one of the plugin script, that plugin script can be loaded in aur/gimp-git. I'm also curious why this can happen.

[bootchk]

OK. As I said previously, maybe the shebang environment has no python2 defined.

If you are in the Arch community, please file a bug report on ...resynthesizer-git.

[jonnyrobbie]

ok, commenting out the sed line (line 27) in the aur's gimp-plugin-resynthesizer-git PKGBUILD got around the issue. I still don't think it's completely solved, but at least it works now.