GNU bug report logs - #77921
GIMP does not start

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 77921 in the body.
You can then email your comments to 77921 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Tomas Volf <~@wolfsden.cz>
To: bug-guix <at> gnu.org
Subject: GIMP does not start
Date: Sat, 19 Apr 2025 13:35:41 +0200

Hello,

I am trying to run GIMP 3.0 and I am getting the following error during
querying the plugins:

--8<---------------cut here---------------start------------->8---
$ gimp
set device 'SynPS/2 Synaptics TouchPad' to mode: disabled
set device 'ELAN901C:00 04F3:2CBD' to mode: disabled
set device 'TPPS/2 Elan TrackPoint' to mode: disabled
set device 'Virtual core XTEST pointer' to mode: disabled
set device 'Logitech Wireless Receiver Mouse' to mode: disabled
set device 'ZSA Technology Labs Moonlander Mark I Consumer Control' to mode: disabled
[script-fu-test-sphere-v3] The catalog directory does not exist: /gnu/store/23az04chw8krp183cv272nymalb3ik39-gimp-3.0.0/lib/gimp/3.0/plug-ins/test-sphere-v3/locale
[script-fu-test-sphere-v3] Override method set_i18n() for the plug-in to customize or disable localization.
[script-fu-test-sphere-v3] Localization disabled
/gnu/store/23az04chw8krp183cv272nymalb3ik39-gimp-3.0.0/lib/gimp/3.0/plug-ins/python-eval/python-eval.py: fatal error: Segmentation fault
/home/wolf/.guix-home/profile/bin/gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): unexpected EOF
/gnu/store/23az04chw8krp183cv272nymalb3ik39-gimp-3.0.0/lib/gimp/3.0/plug-ins/file-openraster/file-openraster.py: fatal error: Segmentation fault
/home/wolf/.guix-home/profile/bin/gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): unexpected EOF

(gjs:10924): GLib-GObject-CRITICAL **: 13:32:41.168: cannot register existing type 'GCancellable'

(gjs:10924): GLib-GObject-CRITICAL **: 13:32:41.168: cannot add private field to invalid (non-instantiatable) type '<invalid>'

(gjs:10924): GLib-CRITICAL **: 13:32:41.168: g_once_init_leave_pointer: assertion 'result != 0' failed
^C/home/wolf/.guix-home/profile/bin/gimp: terminated: Interrupt
--8<---------------cut here---------------end--------------->8---

After those GLib-CRITICAL message it just hangs and I have to ^C it.

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

Message #8 received at 77921 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Tomas Volf <~@wolfsden.cz>
Cc: 77921 <at> debbugs.gnu.org
Subject: Re: bug#77921: GIMP does not start
Date: Wed, 23 Apr 2025 11:41:18 +0900

Hi,

Tomas Volf <~@wolfsden.cz> writes:

> Hello,
>
> I am trying to run GIMP 3.0 and I am getting the following error during
> querying the plugins:
>
> $ gimp
> set device 'SynPS/2 Synaptics TouchPad' to mode: disabled
> set device 'ELAN901C:00 04F3:2CBD' to mode: disabled
> set device 'TPPS/2 Elan TrackPoint' to mode: disabled
> set device 'Virtual core XTEST pointer' to mode: disabled
> set device 'Logitech Wireless Receiver Mouse' to mode: disabled
> set device 'ZSA Technology Labs Moonlander Mark I Consumer Control' to mode: disabled
> [script-fu-test-sphere-v3] The catalog directory does not exist: /gnu/store/23az04chw8krp183cv272nymalb3ik39-gimp-3.0.0/lib/gimp/3.0/plug-ins/test-sphere-v3/locale
> [script-fu-test-sphere-v3] Override method set_i18n() for the plug-in to customize or disable localization.
> [script-fu-test-sphere-v3] Localization disabled
> /gnu/store/23az04chw8krp183cv272nymalb3ik39-gimp-3.0.0/lib/gimp/3.0/plug-ins/python-eval/python-eval.py: fatal error: Segmentation fault
> /home/wolf/.guix-home/profile/bin/gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): unexpected EOF
> /gnu/store/23az04chw8krp183cv272nymalb3ik39-gimp-3.0.0/lib/gimp/3.0/plug-ins/file-openraster/file-openraster.py: fatal error: Segmentation fault
> /home/wolf/.guix-home/profile/bin/gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): unexpected EOF
>
> (gjs:10924): GLib-GObject-CRITICAL **: 13:32:41.168: cannot register existing type 'GCancellable'
>
> (gjs:10924): GLib-GObject-CRITICAL **: 13:32:41.168: cannot add private field to invalid (non-instantiatable) type '<invalid>'
>
> (gjs:10924): GLib-CRITICAL **: 13:32:41.168: g_once_init_leave_pointer: assertion 'result != 0' failed
> ^C/home/wolf/.guix-home/profile/bin/gimp: terminated: Interrupt
>
> After those GLib-CRITICAL message it just hangs and I have to ^C it.

As some data point, I don't reproduce using GNOME with Wayland.  What is
your environment like?  Do you have some 'guix shell' command to
reproduce the failure?

-- 
Thanks,
Maxim

Message #11 received at 77921 <at> debbugs.gnu.org (full text, mbox):

From: James Smith <jsubuntuxp <at> disroot.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: Tomas Volf <~@wolfsden.cz>, 77921 <at> debbugs.gnu.org
Subject: Re: bug#77921: GIMP does not start
Date: Wed, 23 Apr 2025 05:24:11 -0700

Hi,

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> Hi,
>
> Tomas Volf <~@wolfsden.cz> writes:
>
>> Hello,
>>
>> I am trying to run GIMP 3.0 and I am getting the following error during
>> querying the plugins:
>>
>> $ gimp
>> set device 'SynPS/2 Synaptics TouchPad' to mode: disabled
>> set device 'ELAN901C:00 04F3:2CBD' to mode: disabled
>> set device 'TPPS/2 Elan TrackPoint' to mode: disabled
>> set device 'Virtual core XTEST pointer' to mode: disabled
>> set device 'Logitech Wireless Receiver Mouse' to mode: disabled
>> set device 'ZSA Technology Labs Moonlander Mark I Consumer Control' to mode: disabled
>> [script-fu-test-sphere-v3] The catalog directory does not exist: /gnu/store/23az04chw8krp183cv272nymalb3ik39-gimp-3.0.0/lib/gimp/3.0/plug-ins/test-sphere-v3/locale
>> [script-fu-test-sphere-v3] Override method set_i18n() for the plug-in to customize or disable localization.
>> [script-fu-test-sphere-v3] Localization disabled
>> /gnu/store/23az04chw8krp183cv272nymalb3ik39-gimp-3.0.0/lib/gimp/3.0/plug-ins/python-eval/python-eval.py: fatal error: Segmentation fault
>> /home/wolf/.guix-home/profile/bin/gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): unexpected EOF
>> /gnu/store/23az04chw8krp183cv272nymalb3ik39-gimp-3.0.0/lib/gimp/3.0/plug-ins/file-openraster/file-openraster.py: fatal error: Segmentation fault
>> /home/wolf/.guix-home/profile/bin/gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): unexpected EOF
>>
>> (gjs:10924): GLib-GObject-CRITICAL **: 13:32:41.168: cannot register existing type 'GCancellable'
>>
>> (gjs:10924): GLib-GObject-CRITICAL **: 13:32:41.168: cannot add private field to invalid (non-instantiatable) type '<invalid>'
>>
>> (gjs:10924): GLib-CRITICAL **: 13:32:41.168: g_once_init_leave_pointer: assertion 'result != 0' failed
>> ^C/home/wolf/.guix-home/profile/bin/gimp: terminated: Interrupt
>>
>> After those GLib-CRITICAL message it just hangs and I have to ^C it.
>
> As some data point, I don't reproduce using GNOME with Wayland.  What is
> your environment like?  Do you have some 'guix shell' command to
> reproduce the failure?

I'm also able to reproduce this on Sway, Guix channel commit is
a6c96cdb7060ccfc2d0fe27a45b9bcc9590aedd6. GIMP is installed in
~/.guix-profile.

Message #14 received at 77921 <at> debbugs.gnu.org (full text, mbox):

From: Tomas Volf <~@wolfsden.cz>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 77921 <at> debbugs.gnu.org
Subject: Re: bug#77921: GIMP does not start
Date: Sat, 26 Apr 2025 18:14:35 +0200

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> As some data point, I don't reproduce using GNOME with Wayland.  What
> is your environment like?

I am using i3 (so Xorg), with no desktop environment present.

> Do you have some 'guix shell' command to reproduce the failure?

Now that I have tried, I must say I do not, which is interesting.  I
have put together the following command:

guix time-machine -q --commit=7ff20b9e94c429f1160bd8f0db86b153a03e4683 \
    -- shell -C -E ^DISPLAY\$ -E ^DBUS_SESSION_BUS_ADDRESS\$           \
    --expose=/run/user/1000                                            \
    --expose=$HOME/.Xauthority                                         \
    --expose=/tmp/.X11-unix                                            \
    --no-cwd gimp gtk+ -- gimp

Ignoring the fact that I need to provide the gtk+ package (will file a
separate bug for that), the GIMP starts fine.  So there is probably
*some* interference from my environment, but I do not really have any
ideas how to narrow it down.  Will keep looking.

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

Message #17 received at 77921 <at> debbugs.gnu.org (full text, mbox):

From: Tomas Volf <~@wolfsden.cz>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 77921 <at> debbugs.gnu.org, James Smith <jsubuntuxp <at> disroot.org>
Subject: Re: bug#77921: GIMP does not start
Date: Sat, 26 Apr 2025 21:11:28 +0200

Tomas Volf <~@wolfsden.cz> writes:

> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
>
>> As some data point, I don't reproduce using GNOME with Wayland.  What
>> is your environment like?
>
> I am using i3 (so Xorg), with no desktop environment present.
>
>> Do you have some 'guix shell' command to reproduce the failure?
>
> Now that I have tried, I must say I do not, which is interesting.  I
> have put together the following command:
>
> guix time-machine -q --commit=7ff20b9e94c429f1160bd8f0db86b153a03e4683 \
>     -- shell -C -E ^DISPLAY\$ -E ^DBUS_SESSION_BUS_ADDRESS\$           \
>     --expose=/run/user/1000                                            \
>     --expose=$HOME/.Xauthority                                         \
>     --expose=/tmp/.X11-unix                                            \
>     --no-cwd gimp gtk+ -- gimp
>
> Ignoring the fact that I need to provide the gtk+ package (will file a
> separate bug for that), the GIMP starts fine.  So there is probably
> *some* interference from my environment, but I do not really have any
> ideas how to narrow it down.  Will keep looking.

So I have managed to narrow it down to the following environment
variable: GI_TYPELIB_PATH

So on my machine the following command is enough to reproduce the issue:

    guix time-machine -q --commit=7ff20b9e94c429f1160bd8f0db86b153a03e4683 -- shell --pure -E '^GI_TY' gimp gtk+ -- gimp

And the following works as a workaround for running it:

    env -u GI_TYPELIB_PATH gimp

I have no idea what the variable is and from where it gets set, I am not
setting it in my configuration, so it comes from Guix itself (well, some
package I assume).  The value is:

--8<---------------cut here---------------start------------->8---
$ env | sort | grep -i GI_T
GI_TYPELIB_PATH=/home/wolf/.guix-home/profile/lib/girepository-1.0:/home/wolf/.guix-home/profile/lib/girepository-1.0
--8<---------------cut here---------------end--------------->8---

No, I do not know why the value is duplicated.

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

Message #22 received at 77921-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Tomas Volf <~@wolfsden.cz>
Cc: 77921-done <at> debbugs.gnu.org, James Smith <jsubuntuxp <at> disroot.org>
Subject: Re: bug#77921: GIMP does not start
Date: Mon, 28 Apr 2025 13:48:46 +0900

Hi Tomas,

Tomas Volf <~@wolfsden.cz> writes:

[...]

> And the following works as a workaround for running it:
>
>     env -u GI_TYPELIB_PATH gimp

I've made the GI_TYPELIB_PATH wrapping in our gimp package exact (=)
instead of as a suffix (making it as a prefix probably would have worked
too), it should resolve the problem that you have.  See commit 2b4680c6c17.

-- 
Thanks,
Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.