You are not logged in.
It is said that 18-3 build has this applied:
disable python support drop dependency on PyGTK
However, this breaks support for extremely useful plugin called Resynthesizer (basically the only content aware tool for GIMP) that is python based and now I get error message when trying to use it.
Please revert back this change.
Last edited by maboleth (2020-03-18 13:30:47)
Offline
https://lists.archlinux.org/pipermail/a … 29896.html has dev discussion. Short description is this is not likely to happen. PyGTK hasn't been maintained in 9 years, so Arch is finally getting around to dropping it, with Gimp being one of the few things that couldn't be converted to something newer. The impression I got was you'd probably need to wait for gimp 3 to be released. If you can't wait till then you'll have to start making your own build with python support compiled back in
Offline
The GIMP flatpak release (org.gimp.GIMP) might be worth a try.
Offline
https://lists.archlinux.org/pipermail/a … 29896.html has dev discussion. Short description is this is not likely to happen. PyGTK hasn't been maintained in 9 years, so Arch is finally getting around to dropping it, with Gimp being one of the few things that couldn't be converted to something newer. The impression I got was you'd probably need to wait for gimp 3 to be released. If you can't wait till then you'll have to start making your own build with python support compiled back in
Can't we just wait for gimp devs to say more about this? I will raise this question there as well. But the way I see it now, we're dropping support for something that impacts the usability of the program itself (e.g. the only content aware filter in GIMP) because of the other reasons that are not directly impacting anything.
Flatpak is not an option for me due to the nature of flatpaks and its sandbox environment.
I'm a professional photographer, I depend on both GIMP and Rawtherapee.
Last edited by maboleth (2020-03-18 18:50:18)
Offline
You can rebuild gimp 2.10.18 with pygtk support or try gimp-git from AUR.
Last edited by loqs (2020-03-18 19:54:45)
Offline
You can rebuild gimp 2.10.18 with pygtk support or try gimp-git from AUR.
Can you please explain to me what those -git versions do? Are they bleeding-edge releases or... ?
Offline
Building 2.10.18 locally with pygtk would produce the same as 2.10.18-2 until libraries need updating then it would allow you to continue using 2.10.18 with the updated libraries.
gimp-git is tracking the master branch of upstream git development. It has the current version of 2.99 which is actively being developed for gtk3 support.
Offline
I added a new package to AUR called python2-gimp. This package brings back the python2 support for GIMP as an extension, so you don't need to rebuild the whole GIMP package.
Offline
I added a new package to AUR called python2-gimp. This package brings back the python2 support for GIMP as an extension, so you don't need to rebuild the whole GIMP package.
Woohoo, works nicely! Thanks a lot! A time saver for sure! :-)
Offline
mcmillan wrote:https://lists.archlinux.org/pipermail/a … 29896.html has dev discussion. Short description is this is not likely to happen. PyGTK hasn't been maintained in 9 years, so Arch is finally getting around to dropping it, with Gimp being one of the few things that couldn't be converted to something newer. The impression I got was you'd probably need to wait for gimp 3 to be released. If you can't wait till then you'll have to start making your own build with python support compiled back in
Can't we just wait for gimp devs to say more about this? I will raise this question there as well. But the way I see it now, we're dropping support for something that impacts the usability of the program itself (e.g. the only content aware filter in GIMP) because of the other reasons that are not directly impacting anything.
To be honest, I wasn't really thrilled with this change either, because I don't believe we should be in any rush to remove it when upstream is in the process of porting it anyway. We can allow the software to retain valuable features. That being said, thanks to City-busz for finding a fairly low-impact way to keep on using this without rebuilding all of gimp.
I guess I'll retract my private suggestion to the gimp package maintainer to revert that change.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
^ Well yes, even GIMP developer said to me like - ask your Arch guys to try to wait a bit, GIMP 3 will use PyGObject (code is already in the source tree) and Python 3. Maybe if they could just hang a bit longer, it would be more helpful to people rather than just remove a very important feature of GIMP.
But anyway, now that City-bus made this was just awesome. New GIMP users that find some of their plugins not working should be advised of that AUR package as the easiest workaround that is 100% working.
Offline
Is this related to the beautify plugin as well? Here they just talk about the broken 'simple-border' sub-plugin. But when i use the 'LOMO' filter (that works in preview window) GIMP crashes when applying the filter. Some other filters do work though.
sys2064
Offline
^ If your filter has .py extension or says 'python' in the window, then yes. It is affected. Make sure to install that AUR package that reverts this change.
Last edited by maboleth (2020-03-19 23:42:29)
Offline
Is this related to the beautify plugin as well? Here they just talk about the broken 'simple-border' sub-plugin. But when i use the 'LOMO' filter (that works in preview window) GIMP crashes when applying the filter. Some other filters do work though.
No, that's a C plugin with some scheme files.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
I was wondering if anyone has plugins working with gimp after removal of python2 support in Arch. Is the python2-gimp package the permanent solution for now? Ive tried everything at this point and got nothing working. I tried the AUR -git version and that gave me errors with the gimp-plugin-resynthesizer-git AUR scripts and I also tried the Flatpak. The Flatpak does even find the scripts even if put them in a custom location, likely due to this open issue (https://github.com/flathub/org.gimp.GIMP/issues/22).
Last edited by singha95 (2020-04-21 15:02:38)
Offline
Did you bother reading this thread?
Offline
Did you bother reading this thread?
found what I was looking for thx.
https://gitlab.gnome.org/GNOME/gimp/-/issues/4368
Offline