FS#79230 - [gimp] crashed on editing a layer - error window suggested I report it here

Attached to Project: Arch Linux
Opened by Erik Elverskog (elvesten) - Friday, 28 July 2023, 09:51 GMT
Last edited by Toolybird (Toolybird) - Monday, 28 August 2023, 21:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I was trying to crop a layer in GIMP
The error window suggested I report it here

I got the window when running kill (-7) as I could not close the app otherwise

6.4.6-arch1-1 on a T495s Thinkpad

```
GNU Image Manipulation Program version 2.10.34
git-describe: GIMP_2_10_34
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/13.1.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --enable-languages=ada,c,c++,d,fortran,go,lto,objc,obj-c++ --enable-bootstrap --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --with-build-config=bootstrap-lto --with-linker-hash-style=gnu --with-system-zlib --enable-__cxa_atexit --enable-cet=auto --enable-checking=release --enable-clocale=gnu --enable-default-pie --enable-default-ssp --enable-gnu-indirect-function --enable-gnu-unique-object --enable-libstdcxx-backtrace --enable-link-serialization=1 --enable-linker-build-id --enable-lto --enable-multilib --enable-plugin --enable-shared --enable-threads=posix --disable-libssp --disable-libstdcxx-pch --disable-werror
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.1.1 20230429 (GCC)

# Libraries #
using babl version 0.1.106 (compiled against version 0.1.106)
using GEGL version 0.4.46 (compiled against version 0.4.44)
using GLib version 2.76.4 (compiled against version 2.76.3)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.14 (compiled against version 1.50.14)
using Fontconfig version 2.14.2 (compiled against version 2.14.2)
using Cairo version 1.17.8 (compiled against version 1.17.8)

```
> fatal error: Bus error

Stack trace:
```
/usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x458)[0x7f6769fcb308]
gimp(+0xd4032)[0x5619f8081032]
gimp(+0xd43fe)[0x5619f80813fe]
gimp(+0xd4462)[0x5619f8081462]
/usr/lib/libc.so.6(+0x39ab0)[0x7f67691cfab0]
/usr/lib/libc.so.6(syscall+0x1d)[0x7f67692992ed]
/usr/lib/libglib-2.0.so.0(g_cond_wait+0x47)[0x7f676955cca7]
/usr/lib/libgegl-0.4.so.0(+0x1bc94)[0x7f6769aafc94]
/usr/lib/libglib-2.0.so.0(+0x8cd75)[0x7f6769539d75]
/usr/lib/libc.so.6(+0x8744b)[0x7f676921d44b]
/usr/lib/libc.so.6(+0x10ae40)[0x7f67692a0e40]

```




This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 28 August 2023, 21:17 GMT
Reason for closing:  No response
Comment by Erik Elverskog (elvesten) - Friday, 28 July 2023, 09:52 GMT
btw - kill -7 and then clicking restart did not stop Gimp
kill -9 worked
Comment by Toolybird (Toolybird) - Saturday, 29 July 2023, 00:03 GMT
Thanks for reporting, but...that crash window message is old, outdated and essentially useless to us. It needs to be killed off ASAP.

Unfortunately gimp is very crash prone. We are desperately awaiting the release of gimp 3.0.0.

(sorry for the partial posting...PEBKAC issues at my end... more to come)
Comment by Toolybird (Toolybird) - Saturday, 29 July 2023, 00:13 GMT
One-off crashes we can do very little with. We are only interested if you can *reproduce* the crash easily. If you can, we need you to provide a backtrace with debug symbols from debuginfod [1]. It's usually as simple as this (gdb must be installed) i.e. after experiencing the crash:

$ coredumpctl gdb (then answer y when it asks "Enable debuginfod for this session?")
(gdb) set logging enabled
(gdb) bt (or bt full)

Then post gdb.txt

[1] https://wiki.archlinux.org/title/Debugging/Getting_traces

Loading...