Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
<CAAajCMaC6s3SqiKPincqPu_HBBdAsFEdt1B=dvdjadx7r34...@mail.gmail.com>
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding Gimp 2.8 crashes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
939754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: Gimp
Version: 2.10.8-2+b1
I'm using Debian Bullseye. When I open an image with gimp, it crashes
and I get this message:
```GNU Image Manipulation Program version 2.10.8git-describe:
GIMP_2_10_6-294-ga967e8d2c2C compiler: Using built-in specs. COLLECT
_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-
gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD
_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured
with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' --with-
bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-
languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --
with-gcc-major-version-only --program-suffix=-9 --program-
prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --
libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-
libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --
enable-plugin --enable-default-pie --with-system-zlib --with-target-
system-zlib=auto --enable-multiarch --disable-werror --with-arch-
32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-
multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --
without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model:
posix gcc version 9.2.1 20190827 (Debian 9.2.1-6) using GEGL
version 0.4.12 (compiled against version 0.4.14)using GLib version
2.60.6 (compiled against version 2.60.6)using GdkPixbuf version 2.38.1
(compiled against version 2.38.1)using GTK+ version 2.24.32 (compiled
against version 2.24.32)using Pango version 1.42.3 (compiled against
version 1.42.3)using Fontconfig version 2.13.1 (compiled against
version 2.13.1)using Cairo version 1.16.0 (compiled against version
1.16.0)
```> fatal error: Erreur de segmentation
Stack trace:```/lib/libgimpbase-
2.0.so.0(gimp_stack_trace_print+0x398)[0x7fbc2d84bf98]gimp-
2.10(+0xd1590)[0x55c376106590]gimp-2.10(+0xd19b8)[0x55c3761069b8]gimp-
2.10(+0xd2029)[0x55c376107029]/lib/x86_64-linux-
gnu/libpthread.so.0(+0x13510)[0x7fbc2cd83510]gimp-
2.10(gimp_gegl_mask_is_empty+0x91)[0x55c3764f1411]gimp-
2.10(+0x3b7810)[0x55c3763ec810]gimp-
2.10(+0x42ec18)[0x55c376463c18]gimp-
2.10(+0x3d5b50)[0x55c37640ab50]gimp-
2.10(+0x42f2aa)[0x55c3764642aa]gimp-
2.10(gimp_drawable_set_buffer_full+0x1cb)[0x55c3764099bb]gimp-
2.10(gimp_drawable_set_buffer+0x11d)[0x55c376409f9d]gimp-
2.10(gimp_drawable_new+0x106)[0x55c37640a296]gimp-
2.10(gimp_layer_new+0x90)[0x55c3764674d0]gimp-
2.10(+0x3319cc)[0x55c3763669cc]gimp-
2.10(gimp_procedure_execute+0x237)[0x55c37639f577]gimp-
2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x55c376398a39]gimp
-2.10(gimp_plug_in_handle_message+0x216)[0x55c3763a3626]gimp-
2.10(+0x36cf91)[0x55c3763a1f91]/lib/x86_64-linux-gnu/libglib-
2.0.so.0(g_main_context_dispatch+0x158)[0x7fbc2cf29898]/lib/x86_64-
linux-gnu/libglib-2.0.so.0(+0x4ec88)[0x7fbc2cf29c88]/lib/x86_64-linux-
gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7fbc2cf29f82]gimp-
2.10(gimp_plug_in_manager_call_run+0x5fc)[0x55c3763b335c]gimp-
2.10(+0x376dbe)[0x55c3763abdbe]gimp-
2.10(gimp_procedure_execute+0x237)[0x55c37639f577]gimp-
2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x55c376398a39]gimp
-2.10(gimp_pdb_execute_procedure_by_name+0x3cd)[0x55c376398efd]gimp-
2.10(file_open_image+0x33d)[0x55c3764996fd]gimp-
2.10(file_open_with_proc_and_display+0x29d)[0x55c37649a64d]gimp-
2.10(+0x113573)[0x55c376148573]gimp-
2.10(+0x1138b7)[0x55c3761488b7]/lib/x86_64-linux-gnu/libgobject-
2.0.so.0(g_closure_invoke+0x19d)[0x7fbc2d00fe8d]/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(+0x27555)[0x7fbc2d023555]/lib/x86_64-linux-
gnu/libgobject-
2.0.so.0(g_signal_emit_valist+0xd8e)[0x7fbc2d02c4ae]/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7fbc2d02cb6f]/lib/x86_64-
linux-gnu/libgobject-
2.0.so.0(g_closure_invoke+0x19d)[0x7fbc2d00fe8d]/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(+0x27555)[0x7fbc2d023555]/lib/x86_64-linux-
gnu/libgobject-
2.0.so.0(g_signal_emit_valist+0xd8e)[0x7fbc2d02c4ae]/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7fbc2d02cb6f]/lib/x86_64-
linux-gnu/libgtk-x11-2.0.so.0(+0x8dd4e)[0x7fbc2d9f8d4e]/lib/x86_64-
linux-gnu/libgdk-x11-2.0.so.0(+0x1e804)[0x7fbc2d8d2804]/lib/x86_64-
linux-gnu/libglib-2.0.so.0(+0x4f323)[0x7fbc2cf2a323]/lib/x86_64-linux-
gnu/libglib-
2.0.so.0(g_main_context_dispatch+0x158)[0x7fbc2cf29898]/lib/x86_64-
linux-gnu/libglib-2.0.so.0(+0x4ec88)[0x7fbc2cf29c88]/lib/x86_64-linux-
gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7fbc2cf29f82]gimp-
2.10(app_run+0x36e)[0x55c376105d7e]gimp-
2.10(main+0x36e)[0x55c37610564e]/lib/x86_64-linux-
gnu/libc.so.6(__libc_start_main+0xeb)[0x7fbc2cbd4bbb]gimp-
2.10(_start+0x2a)[0x55c3761057da]
```
--- End Message ---
--- Begin Message ---
On Wed, Sep 18, 2019 at 5:21 AM Bernhard Übelacker
<bernha...@mailbox.org> wrote:
> Now that gegl 0.4.14-2 transitioned to testing,
> gimp 2.10.8-2+b1 should work as expected in testing.
> (User confirmation in [1].)
>
> If there is nothing that could be done in gimp to avoid
> such situations (fxied version dependency to gegl?),
> I guess this bugs can be closed?
Thank you for merging the bugs. I'm going ahead and closing this bug now.
Jeremy
--- End Message ---
