-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An error occurred running python_fu_heal_selection #10
Comments
I tried to build from source, which I needed intltool, which was easy enough to install So... after that (and more), I think I'm just going to stick to the heal / clone tools manually for now haha. |
Actually, I was able to finally fix this by making a symbolic link to "fake" having a newer dynamically linked library.
Major thanks to http://homepage.agrl.ethz.ch/eugsterw/knowhow/gimp-resynthesizer/ UPDATE: My old comment is above, but keep reading to my newer comment here for a more robust solution. |
So rebuild the plugin from source solved the original problem of running pythyon_fu_heal_selection error? |
I have the exact same issue, however none of the solutions given above is actually working. I'm running latest gimp provided by brew (2.10) and running on BigSur M1 silicon. Traceback (most recent call last): Is there a chance that the build is having issues? |
@pqs0103
UPDATE: cd /Applications/GIMP-2.10.app/Contents/Resources/lib
ln -s libintl.8.dylib libintl.9.dylib Confirmed to work on
Additional information at: |
I was able to fix the problem after brew install some software to finally bring in the libintl.8.dylib into my laptop and do the symbolic link trick. Thank you @mattpopovich |
I found that I needed to add the symlink from this location instead, which is also suggested on: https://gitlab.gnome.org/GNOME/gimp/-/issues/6529 Hoping this tip helps others.
|
THANK YOU! On MacOS Monterey and this is the only solution that worked! |
I guess I should leave this open as while I have found a solution, it's not actually "fixed"... |
I have this same issue, but I am on Windows. |
I had to reinstall GIMP recently due to lockups when loading more complex files. After reinstalling GIMP 2.10.32-1, the Resynthesizer plug-in will give an error. I removed GIMP, the GIMP folder from Application Support, and the GIMP preference file. Then I did the following: Installed: GIMP Version: 2.10.32 (revision 1) Steps tried: reinstalling GIMP, removing GIMP, tried with HomeBrew install -- all failed with the Resynthesizer plug-in. Python error: Gimp error: I must be missing something obvious. This all worked with the previous version of GIMP. Thank you for your input. |
@OdysseyScorpio @KCapwell i was able to "fix" this by downloading i'm using the latest GIMP Portable |
With macOS Monterey 12.7.5 and Gimp 2.10.32, I was able to get the plugin working thus: find /opt/ -name 'libintl*' |
I had this error occur once on my main Mac running Catalina 10.15.7 (Intel i7). I have a spare with a fresh build of Catalina 10.15.7 (older i7) that returned the same issue. I am running GIMP 2.10.22 (revision 3) on Mac.
I downloaded ResynthesizerPlugin-Gimp-2.10-osx.tgz from the "Continuous build" release.
I then extracted the archive to both
/Users/username/Library/Application Support/GIMP/2.10/plug-ins
and/Applications/GIMP-2.10.app/Contents/Resources/lib/gimp/2.0/plug-ins
. Both locations resulted in the same error.When trying to run
Filters
->Enhance
->Heal selection…
I get:And
I’ve made sure that all the files I exported from the archive have executable permission via
chmod u+x
Looks like others are having a similar issue judging from the newest comments on this YouTube video.
I’m going to try and mess around and build the files myself instead of just taking them from the release (which was 3 years ago).
The text was updated successfully, but these errors were encountered: