The gimp-3.0 python console won't open (crashes with segfault) if both /usr/lib/girepository-1.0 and /usr/lib64/girepository-1.0 are present. (This is the case when wine is installed on an x86_64 machine.) Moving /usr/lib/girepository-1.0 out of the way (to /usr/lib/WAS-girepository-1.0, say) avoids the problem. Running "lsof -p..." on the script-fu process shows this. Reproducible: Always Steps to Reproduce: 1. Start gimp. 2. Open python console: Filters->Development->Python-Fu->Python Console Actual Results: No console appears. If gimp was started in a terminal, you'll see a segfault or malloc error message. Expected Results: Python console opens. Additional Information: "lsof -p..." shows the problem clearly: $ lsof -p 213004 | grep /girepository script-fu 213004 tom mem REG 0,41 28121110 /usr/lib/girepository-1.0/GdkPixbuf-2.0.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 28144038 /usr/lib64/girepository-1.0/Babl-0.1.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 28144350 /usr/lib64/girepository-1.0/Gegl-0.4.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 28120496 /usr/lib/girepository-1.0/Gio-2.0.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 28120518 /usr/lib/girepository-1.0/HarfBuzz-0.0.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 28121701 /usr/lib/girepository-1.0/Pango-1.0.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 28120492 /usr/lib/girepository-1.0/GLib-2.0.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 28120495 /usr/lib/girepository-1.0/GObject-2.0.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 27694685 /usr/lib64/girepository-1.0/cairo-1.0.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 28145952 /usr/lib64/girepository-1.0/Gimp-3.0.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 28120494 /usr/lib/girepository-1.0/GModule-2.0.typelib (path dev=0,43) script-fu 213004 tom mem REG 0,41 27694687 /usr/lib64/girepository-1.0/freetype2-2.0.typelib (path dev=0,43)
Thanks for the report and analysis! I can reproduce this on both Fedora 41 and 42, but so far have little to no idea what’s going on.
Ahh: --- 8< --- # cat /usr/lib64/gimp/3.0/environ/python.env : GI_TYPELIB_PATH=${gimp_installation_dir}/lib/girepository-1.0/ --- >8 --- Try commenting out this line in the file (prefix it with "#"), or move it out of the way completely as a workaround. Let me know if this works around the issue for you, too.
Removing EasyFix keyword, I assume it’s not trivial to do this properly and not break e.g. 32bit GIMP on a 64bit machine.
Yes, commenting out GI_TYPELIB_PATH fixes this for me, thanks.
(In reply to Nils Philippsen from comment #3) > Removing EasyFix keyword, I assume it’s not trivial to do this properly and > not break e.g. 32bit GIMP on a 64bit machine. The RPM knows what architecture it was built for, maybe that can tell gimp where to look.
(In reply to Tom Killian from comment #5) > (In reply to Nils Philippsen from comment #3) > > Removing EasyFix keyword, I assume it’s not trivial to do this properly and > > not break e.g. 32bit GIMP on a 64bit machine. > > The RPM knows what architecture it was built for, maybe that can tell gimp > where to look. Yeah, I want to come up with something palatable to upstream, so other distros can take advantage of it, too.
*** Bug 2369649 has been marked as a duplicate of this bug. ***
FEDORA-2025-356efe32d2 (gimp-3.0.4-3.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-356efe32d2
FEDORA-2025-4f3bde861c (gimp-3.0.4-3.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-4f3bde861c
FEDORA-2025-356efe32d2 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-356efe32d2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-356efe32d2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-4f3bde861c has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4f3bde861c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4f3bde861c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
(In reply to Fedora Update System from comment #11) > FEDORA-2025-4f3bde861c has been pushed to the Fedora 41 testing repository. > Soon you'll be able to install the update with the following command: > `sudo dnf upgrade --enablerepo=updates-testing --refresh > --advisory=FEDORA-2025-4f3bde861c` > You can provide feedback for this update here: > https://bodhi.fedoraproject.org/updates/FEDORA-2025-4f3bde861c > > See also https://fedoraproject.org/wiki/QA:Updates_Testing for more > information on how to test updates. Works perfectly, thanks.
FEDORA-2025-356efe32d2 (gimp-3.0.4-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-4f3bde861c (gimp-3.0.4-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.