Bug 2369440

Summary: gimp-3.0 on x86_64 uses files from glib2.i686 instead of glib2.x86_64 if both are installed (e.g. by wine)
Product: [Fedora] Fedora Reporter: Tom Killian <tom.killian>
Component: gimpAssignee: Nils Philippsen <nphilipp>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 41CC: jridky, nididak, nphilipp, phracek, zdohnal
Target Milestone: ---Keywords: Bugfix, Desktop
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gimp-3.0.4-3.fc42 gimp-3.0.4-3.fc41 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-06-07 06:46:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tom Killian 2025-05-30 15:29:40 UTC
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)

Comment 1 Nils Philippsen 2025-05-30 16:50:35 UTC
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.

Comment 2 Nils Philippsen 2025-05-30 17:05:50 UTC
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.

Comment 3 Nils Philippsen 2025-05-30 17:07:42 UTC
Removing EasyFix keyword, I assume it’s not trivial to do this properly and not break e.g. 32bit GIMP on a 64bit machine.

Comment 4 Tom Killian 2025-05-30 17:47:51 UTC
Yes, commenting out GI_TYPELIB_PATH fixes this for me, thanks.

Comment 5 Tom Killian 2025-05-30 18:00:54 UTC
(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.

Comment 6 Nils Philippsen 2025-05-30 18:35:07 UTC
(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.

Comment 7 Nils Philippsen 2025-06-02 12:30:54 UTC
*** Bug 2369649 has been marked as a duplicate of this bug. ***

Comment 8 Fedora Update System 2025-06-02 16:51:28 UTC
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

Comment 9 Fedora Update System 2025-06-02 16:51:29 UTC
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

Comment 10 Fedora Update System 2025-06-03 02:52:50 UTC
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.

Comment 11 Fedora Update System 2025-06-03 03:54:33 UTC
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.

Comment 12 Tom Killian 2025-06-03 15:23:12 UTC
(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.

Comment 13 Fedora Update System 2025-06-07 06:46:20 UTC
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.

Comment 14 Fedora Update System 2025-06-11 03:51:47 UTC
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.