GNOME Bugzilla – Bug 794865
crash on load
Last modified: 2018-04-18 11:19:04 UTC
GNU Image Manipulation Program version 2.10.0-RC1 git-describe: GIMP_2_9_8-784-g956ca8e3a3 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release --enable-default-pie --enable-default-ssp Thread model: posix gcc version 7.3.1 20180312 (GCC) using GEGL version 0.3.31 (compiled against version 0.3.31) using GLib version 2.56.0 (compiled against version 2.56.0) using GdkPixbuf version 2.36.11 (compiled against version 2.36.11) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.41.1 (compiled against version 1.41.1) using Fontconfig version 2.13.0 (compiled against version 2.13.0) using Cairo version 1.15.11 (compiled against version 1.15.11) > fatal error: Segmentation fault Stack trace: /usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x170)[0x7f0a8e7d92d0] gimp-2.10(+0xc0b84)[0x556ff0091b84] gimp-2.10(+0xc1328)[0x556ff0092328] gimp-2.10(+0xc1a59)[0x556ff0092a59] /usr/lib/libpthread.so.0(+0x11dd0)[0x7f0a8ab16dd0] /usr/lib/libc.so.6(+0x8e67e)[0x7f0a8a7dc67e] /usr/lib/libmypaint-1.3.so.0(mypaint_brush_setting_from_cname+0x2c)[0x7f0a8e0edd5c] /usr/lib/libmypaint-1.3.so.0(mypaint_brush_from_string+0x1b4)[0x7f0a8e0ed974] gimp-2.10(gimp_mybrush_load+0x17a)[0x556ff03e874a] gimp-2.10(+0x3b0f81)[0x556ff0381f81] gimp-2.10(+0x3b117e)[0x556ff038217e] gimp-2.10(+0x3b139b)[0x556ff038239b] gimp-2.10(gimp_data_factory_data_init+0x93)[0x556ff0382d03] gimp-2.10(gimp_data_factories_load+0xea)[0x556ff034f07a] gimp-2.10(gimp_restore+0x99)[0x556ff034c429] gimp-2.10(app_run+0x484)[0x556ff0091614] gimp-2.10(main+0x364)[0x556ff0090d84] /usr/lib/libc.so.6(__libc_start_main+0xea)[0x7f0a8a76ef4a] gimp-2.10(_start+0x2a)[0x556ff0090f3a]
Hello, Thanks for the report. I see you are using Archlinux. This is most likely a duplicate of bug 794818. It looks like Archlinux has some dependency issue either with libmypaint or mypaint-brushes. In this other bug report, the problem was "fixed" by reinstalling libmypaint apparently. Apparently there seems to be a package bug. Could you please submit a bug report to Archlinux?
I added a comment to the AUR gimp-devel package page AUR packages are user packages not 'official' stuff so this can't easily be stompted out as normal package update processes don't check user packages so they can get out of date without knowing it seeing one comment it looked like just libmypaint needed recompile due to ABI json-c breakage
*** This bug has been marked as a duplicate of bug 794818 ***